[
https://issues.apache.org/jira/browse/HADOOP-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637825#action_12637825
]
Amar Kamat commented on HADOOP-4018:
------------------------------------
+1.
The reason why I proposed the new name is because it becomes easier to relate.
_mapred.job.tasks.maximum_ would mean that there is an attribute _maximum_ for
a component _tasks_ of an entity _job_ under the _mapred_ umbrella. But I am
ok with the current name too.
> limit memory usage in jobtracker
> --------------------------------
>
> Key: HADOOP-4018
> URL: https://issues.apache.org/jira/browse/HADOOP-4018
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: maxSplits.patch, maxSplits10.patch, maxSplits2.patch,
> maxSplits3.patch, maxSplits4.patch, maxSplits5.patch, maxSplits6.patch,
> maxSplits7.patch, maxSplits8.patch, maxSplits9.patch
>
>
> We have seen instances when a user submitted a job with many thousands of
> mappers. The JobTracker was running with 3GB heap, but it was still not
> enough to prevent memory trashing from Garbage collection; effectively the
> Job Tracker was not able to serve jobs and had to be restarted.
> One simple proposal would be to limit the maximum number of tasks per job.
> This can be a configurable parameter. Is there other things that eat huge
> globs of memory in job Tracker?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
