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 "Arun C Murthy (Commented) (JIRA)" <ji...@apache.org> on 2011/10/04 06:35:34 UTC
[jira] [Commented] (MAPREDUCE-3126) mr job stuck because reducers
using all slots and mapper isn't scheduled
[ https://issues.apache.org/jira/browse/MAPREDUCE-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119893#comment-13119893 ]
Arun C Murthy commented on MAPREDUCE-3126:
------------------------------------------
Thomas, could glean anything from the logs?
Also, can you check if any NM was 'lost' i.e. crashed - there is corner-case with headroom calculations when cluster-capacity changes, I'm wondering if that was the cause here?
> mr job stuck because reducers using all slots and mapper isn't scheduled
> ------------------------------------------------------------------------
>
> Key: MAPREDUCE-3126
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3126
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Thomas Graves
> Priority: Blocker
> Fix For: 0.23.0
>
>
> The command in MAPREDUCE-3124 run and this job got hung with 1 Map task waiting for resources and 7 Reducers running (2 waiting). The mapper got scheduler, then AM scheduled the reducers, the map task failed and tried to start a new attempt but reducers were using all the slots.
> I will try to add some more info from the logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira