[
https://issues.apache.org/jira/browse/HADOOP-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859198#action_12859198
]
Hemanth Yamijala commented on HADOOP-6439:
------------------------------------------
bq. @Hemanth, I don't think we need to update patches for branch 0.21, as per
discussion in general mailing list, branch 0.21 will be cut from trunk itself.
Ah. If that's so, then we are good to go. I will wait for Tom's / anyone else's
confirmation on this.
> 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: V.V.Chaitanya Krishna
> Priority: Blocker
> Fix For: 0.21.0, 0.22.0
>
> Attachments: HADOOP-6439-1.patch, HADOOP-6439-2.patch,
> HADOOP-6439-3.patch, HADOOP-6439-4.patch, HADOOP-6439-5.patch,
> HADOOP-6439-6.patch, HADOOP-6439-6.patch, HADOOP-6439-7.patch, 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.
