[
https://issues.apache.org/jira/browse/YARN-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496251#comment-13496251
]
Hadoop QA commented on YARN-212:
--------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12553260/yarn-212.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/144//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/144//console
This message is automatically generated.
> NM state machine ignores an APPLICATION_CONTAINER_FINISHED event when it
> shouldn't
> ----------------------------------------------------------------------------------
>
> Key: YARN-212
> URL: https://issues.apache.org/jira/browse/YARN-212
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 0.23.4, 2.0.1-alpha
> Reporter: Nathan Roberts
> Assignee: Nathan Roberts
> Priority: Blocker
> Attachments: yarn-212.txt, yarn-212.txt
>
>
> The NM state machines can make the following two invalid state transitions
> when a speculative attempt is killed shortly after it gets started. When this
> happens the NM keeps the log aggregation context open for this application
> and therefore chews up FDs and leases on the NN, eventually running the NN
> out of FDs and bringing down the entire cluster.
> 2012-11-07 05:36:33,774 [AsyncDispatcher event handler] WARN
> org.apache.hadoop.yarn.server.nodemanager.containermanager.application.Application:
> Can't handle this event at current state
> org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event:
> APPLICATION_CONTAINER_FINISHED at INITING
> 2012-11-07 05:36:33,775 [AsyncDispatcher event handler] WARN
> org.apache.hadoop.yarn.server.nodemanager.containermanager.container.Container:
> Can't handle this event at current state: Current: [DONE], eventType:
> [INIT_CONTAINER]
> org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event:
> INIT_CONTAINER at DONE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
