hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-200) mapred.map.tasks and mapred.reduce.tasks should be determined automatically by default
Date Tue, 29 Sep 2009 20:07:07 GMT

    [ 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.


Mime
View raw message