You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2011/07/16 18:59:59 UTC
[jira] [Moved] (MAPREDUCE-2700) dynamic configuration of
mapred.map/reduce.tasks
[ https://issues.apache.org/jira/browse/MAPREDUCE-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J moved HADOOP-608 to MAPREDUCE-2700:
-------------------------------------------
Component/s: (was: conf)
job submission
Issue Type: New Feature (was: Wish)
Key: MAPREDUCE-2700 (was: HADOOP-608)
Project: Hadoop Map/Reduce (was: Hadoop Common)
> dynamic configuration of mapred.map/reduce.tasks
> ------------------------------------------------
>
> Key: MAPREDUCE-2700
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2700
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: job submission
> Reporter: Johannes Zillmann
> Priority: Minor
>
> Since the optimal value for these 2 configuration properties heavily depends on the numer of nodes, also examined here
> http://wiki.apache.org/lucene-hadoop/HowManyMapsAndReduces
> would it be not more comfortable to configure relations to numberOfNodes ?
> So you hav'nt to change it all the time the number of nodes changes...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira