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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2009/09/29 22:07:07 UTC
[jira] Commented: (MAPREDUCE-200) mapred.map.tasks and
mapred.reduce.tasks should be determined automatically by default
[ https://issues.apache.org/jira/browse/MAPREDUCE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760684#action_12760684 ]
Allen Wittenauer commented on MAPREDUCE-200:
--------------------------------------------
I know the bug is still open, etc, but has there been any movement on this? Reducing the number of params to configure would be a good thing, and this one seems to be particularly good to eliminate.
> mapred.map.tasks and mapred.reduce.tasks should be determined automatically by default
> --------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-200
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-200
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Reporter: Doug Cutting
>
> The default values for mapred.map.tasks and mapred.reduce.tasks should be empty or -1, signalling that the framework should use an dynamically-determined default. An appropriate default is perhaps the number of map and reduce slots in the cluster, since FileInputFormat interprets mapred.map.tasks as a minimum.
> This would remove a common area of misconfiguration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.