hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1252) Shuffle deadlocks on wrong number of maps
Date Tue, 01 Dec 2009 08:19:20 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784114#action_12784114

Owen O'Malley commented on MAPREDUCE-1252:

This patch is necessary to suppress the warnings, but doesn't fix the problem.

The problem is that I was using a configuration with the old attribute name. The attribute
name isn't being translated during the xml loading. I'm not sure how it is happening, but
in some context, we get 2 and others 12. When I change the config to use the new attribute
name, it all goes away.

I suspect this is caused by a bug in HADOOP-6105.

> Shuffle deadlocks on wrong number of maps
> -----------------------------------------
>                 Key: MAPREDUCE-1252
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1252
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: task
>    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
> 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.

View raw message