You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2013/10/07 18:32:42 UTC

[jira] [Created] (YARN-1282) CONTAINER_KILLED_ON_REQUEST is considered invalid event for state CONTAINER_CLEANEDUP_AFTER_KILL

Ted Yu created YARN-1282:
----------------------------

             Summary: CONTAINER_KILLED_ON_REQUEST is considered invalid event for state CONTAINER_CLEANEDUP_AFTER_KILL
                 Key: YARN-1282
                 URL: https://issues.apache.org/jira/browse/YARN-1282
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Ted Yu
            Priority: Minor
         Attachments: TestFreezeThawLiveRegionService.out

When running TestFreezeThawLiveRegionService in HOYA, I observed the following exception in log:
{code}
2013-10-07 09:17:18,493 [AsyncDispatcher event handler] INFO  nodemanager.NMAuditLogger (NMAuditLogger.java:logSuccess(89)) - USER=tyu  OPERATION=Container Finished - Killed TARGET=ContainerImpl  RESULT=SUCCESS  APPID=application_1381162545230_0002  CONTAINERID=container_1381162545230_0002_01_000003
2013-10-07 09:17:18,493 [AsyncDispatcher event handler] INFO  container.Container (ContainerImpl.java:handle(871)) - Container container_1381162545230_0002_01_000003 transitioned from CONTAINER_CLEANEDUP_AFTER_KILL to DONE
2013-10-07 09:17:18,494 [AsyncDispatcher event handler] INFO  container.Container (ContainerImpl.java:handle(871)) - Container container_1381162545230_0002_01_000002 transitioned from KILLING to CONTAINER_CLEANEDUP_AFTER_KILL
2013-10-07 09:17:18,494 [AsyncDispatcher event handler] WARN  container.Container (ContainerImpl.java:handle(867)) - 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:864)
  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:685)
  at org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ContainerEventDispatcher.handle(ContainerManagerImpl.java:678)
  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:680)
{code}
Looking at ContainerImpl.java, CONTAINER_KILLED_ON_REQUEST is not defined as an expected state for CONTAINER_CLEANEDUP_AFTER_KILL.



--
This message was sent by Atlassian JIRA
(v6.1#6144)