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 "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/11/01 16:15:22 UTC

[jira] [Comment Edited] (MAPREDUCE-5481) Uber job reducers hang waiting to shuffle map outputs

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

Jason Lowe edited comment on MAPREDUCE-5481 at 11/1/13 3:13 PM:
----------------------------------------------------------------

This is not localized to just TestUberAM, as all uber jobs with reducers will currently hang like this.  This appears to have been broken when MAPREDUCE-434 was committed, since it changed the way reducers locate map outputs when not running via normal containers.

Updating the summary to better reflect the issue.


was (Author: jlowe):
This is not localized to just TestUberAM, as all uber jobs with reducers will currently hang like this.  I believe the test is This appears to have been broken when MAPREDUCE-434 was committed, as that changed the way reducers locate map outputs when not running via normal containers.

Updating the summary to better reflect the issue.

> Uber job reducers hang waiting to shuffle map outputs
> -----------------------------------------------------
>
>                 Key: MAPREDUCE-5481
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5481
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, test
>    Affects Versions: 3.0.0
>            Reporter: Jason Lowe
>            Assignee: Xuan Gong
>            Priority: Blocker
>         Attachments: syslog
>
>
> TestUberAM has been timing out on trunk for some time now and surefire then fails the build.  I'm not able to reproduce it locally, but the Jenkins builds have been seeing it fairly consistently.  See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1529/console



--
This message was sent by Atlassian JIRA
(v6.1#6144)