You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Allen Wittenauer (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/02 18:47:33 UTC
[jira] [Resolved] (MAPREDUCE-1206) Need a better answer for "how
many reduces?"
[ https://issues.apache.org/jira/browse/MAPREDUCE-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-1206.
-----------------------------------------
Resolution: Won't Fix
> Need a better answer for "how many reduces?"
> --------------------------------------------
>
> Key: MAPREDUCE-1206
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1206
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Allen Wittenauer
>
> http://hadoop.apache.org/common/docs/current/mapred_tutorial.html#Reducer
> --snip--
> How Many Reduces?
> The right number of reduces seems to be 0.95 or 1.75 multiplied by (<no. of nodes> * mapred.tasktracker.reduce.tasks.maximum).
> --snip--
> Sure, if you only ever run one job on your grid. There should really be a better answer here, especially explaining what the impact is of a high/low number when chaining multiple map/reduce jobs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira