Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
Currently, controlling the number of map/reduce tasks is a hell.
I've tried for it many times, and it doesn't work right. Also, I am not the only one person, who seems to have this problem.
There must be a better way to do it.
Here's my proposal:
add following functions to Job:
setNumberOfMappersPerNode(int);
setNumberOfReducersPerNode(int);
setMaxMemoryPerMapper(int);
setMaxMemoryPerReducer(int);