You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Ravi Gummadi (JIRA)" <ji...@apache.org> on 2009/12/14 12:55:18 UTC
[jira] Moved: (HADOOP-6439) Shuffle deadlocks on wrong number of
maps
[ https://issues.apache.org/jira/browse/HADOOP-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ravi Gummadi moved MAPREDUCE-1252 to HADOOP-6439:
-------------------------------------------------
Component/s: (was: task)
conf
Fix Version/s: (was: 0.22.0)
(was: 0.21.0)
0.22.0
0.21.0
Affects Version/s: (was: 0.22.0)
(was: 0.21.0)
0.22.0
0.21.0
Key: HADOOP-6439 (was: MAPREDUCE-1252)
Project: Hadoop Common (was: Hadoop Map/Reduce)
> Shuffle deadlocks on wrong number of maps
> -----------------------------------------
>
> Key: HADOOP-6439
> URL: https://issues.apache.org/jira/browse/HADOOP-6439
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Priority: Blocker
> Fix For: 0.21.0, 0.22.0
>
> Attachments: mr-1252.patch
>
>
> The new shuffle assumes that the number of maps is correct. The new JobSubmitter sets the old value. Something misfires in the middle causing:
> 09/12/01 00:00:15 WARN conf.Configuration: mapred.job.split.file is deprecated. Instead, use mapreduce.job.splitfile
> 09/12/01 00:00:15 WARN conf.Configuration: mapred.map.tasks is deprecated. Instead, use mapreduce.job.maps
> But my reduces got stuck at 2 maps / 12 when there were only 2 maps in the job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.