[
https://issues.apache.org/jira/browse/MAPREDUCE-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103520#comment-13103520
]
Hadoop QA commented on MAPREDUCE-2995:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12494207/MAPREDUCE-2995-20110913.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 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/714//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/714//console
This message is automatically generated.
> MR AM crashes when a container-launch hangs on a faulty NM
> ----------------------------------------------------------
>
> Key: MAPREDUCE-2995
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2995
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-2995-20110913.txt
>
>
> AM tries to launch containers on a faulty node which blocks several/all of
> the {{StartContainer}} requests. Eventually, RM expires the
> container-allocations, informs the AM about container-expiry. But AM crashes
> with an INTERNAL_ERROR as the event is unexpected.
> {code}
> 11/09/12 14:11:38 ERROR impl.TaskAttemptImpl: Can't handle this event at
> current state
> org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event:
> TA_CONTAINER_COMPLETED at ASSIGNED
> at
> org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:297)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:39)
> at
> org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:439)
> at
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.handle(TaskAttemptImpl.java:903)
> at
> org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl.handle(TaskAttemptImpl.java:127)
> at
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster$TaskAttemptEventDispatcher.handle(MRAppMaster.java:543)
> at
> org.apache.hadoop.mapreduce.v2.app.MRAppMaster$TaskAttemptEventDispatcher.handle(MRAppMaster.java:536)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:113)
> at
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:75)
> at java.lang.Thread.run(Thread.java:619)
> {code}
> Found this on a big cluster where [~karams] was trying to get sort running.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
