[
https://issues.apache.org/jira/browse/HADOOP-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646402#action_12646402
]
Christian Kunz commented on HADOOP-4295:
----------------------------------------
I talked with Sameer offline and we agreed to use a work-around based on the
scheduler till a more general solution for resource monitoring and utilization
is available.
> job-level configurable mapred.map.tasks.maximum and
> mapred.reduce.tasks.maximum
> --------------------------------------------------------------------------------
>
> Key: HADOOP-4295
> URL: https://issues.apache.org/jira/browse/HADOOP-4295
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Christian Kunz
>
> Right now mapred.tasktracker.map.tasks.maximum and
> mapred.tasktracker.reduce.tasks.maximum are set on the tasktracker level.
> In absense of a smart tasktracker monitoring resources and deciding in an
> adaptive manner how many tasks can be run simultaneously, it would be nice to
> move these two configuration options to the job level. This would make it
> easier to optimize the performance of a batch of jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
