[
https://issues.apache.org/jira/browse/MAPREDUCE-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124909#comment-13124909
]
Hadoop QA commented on MAPREDUCE-3126:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12498563/MAPREDUCE-3126.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/984//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/984//console
This message is automatically generated.
> 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
> Assignee: Arun C Murthy
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-3126.patch
>
>
> 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
