In MRv1 we had the below two configurable parameters to set the number of Map and reduce slots per Node.
mapred.tasktracker.map.tasks.maximum
mapred.tasktracker.reduce.tasks.maximum
Also it was advisable to have number of Map slots little higher than the number of Reduce slots. Ideal number of reducers for a Map Reduce job would be equal to or greater than number of reduce slots available in the cluster.
Please correct if my above understanding is not correct wrt MRv1...
In MRv2 we dont have the concept of slots anymore, instead containers provide the required memory and CPU for Map/Reduce taks execution.
Here comes my question, How to decide on number of reducers for any Map Reduce job in MRv2 ?
Thanks