hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-1159) NodeManager reports Invalid event: CONTAINER_KILLED_ON_REQUEST at CONTAINER_CLEANEDUP_AFTER_KILL
Date Fri, 06 Sep 2013 09:55:55 GMT
Alejandro Abdelnur created YARN-1159:
----------------------------------------

             Summary: NodeManager reports  Invalid event: CONTAINER_KILLED_ON_REQUEST at CONTAINER_CLEANEDUP_AFTER_KILL
                 Key: YARN-1159
                 URL: https://issues.apache.org/jira/browse/YARN-1159
             Project: Hadoop YARN
          Issue Type: Bug
          Components: nodemanager
    Affects Versions: 2.1.0-beta
            Reporter: Alejandro Abdelnur
             Fix For: 2.1.1-beta


When running MR PI, which runs successfully, the NM log reports:

{code}
2013-09-06 11:45:29,368 INFO org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl:
Sending out status for container: container_id { app_attempt_id { application_id { id: 5 cluster_timestamp:
1378450335207 } attemptId: 1 } id: 4 } state: C_RUNNING diagnostics: "Container killed by
the ApplicationMaster.\n" exit_status: -1000
2013-09-06 11:45:29,390 WARN org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor:
Exit code from container container_1378450335207_0005_01_000004 is : 143
2013-09-06 11:45:29,425 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.container.Container:
Container container_1378450335207_0005_01_000004 transitioned from KILLING to CONTAINER_CLEANEDUP_AFTER_KILL
2013-09-06 11:45:29,426 WARN org.apache.hadoop.yarn.server.nodemanager.containermanager.container.Container:
Can't handle this event at current state: Current: [CONTAINER_CLEANEDUP_AFTER_KILL], eventType:
[CONTAINER_KILLED_ON_REQUEST]
org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: CONTAINER_KILLED_ON_REQUEST
at CONTAINER_CLEANEDUP_AFTER_KILL
	at org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:305)
	at org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
	at org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
	at org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:853)
	at org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:73)
	at org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:684)
	at org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:677)
	at org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:134)
	at org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:81)
	at java.lang.Thread.run(Thread.java:722)
2013-09-06 11:45:29,426 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.container.Container:
Container container_1378450335207_0005_01_000004 transitioned from CONTAINER_CLEANEDUP_AFTER_KILL
to null
{code}

--
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

Mime
View raw message