hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Omkar Vinit Joshi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-98) NM Application invalid state transition on reboot command from RM
Date Mon, 15 Apr 2013 20:26:16 GMT

     [ https://issues.apache.org/jira/browse/YARN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Omkar Vinit Joshi resolved YARN-98.
-----------------------------------

    Resolution: Duplicate

After yarn-495 fix this issue is not reproducible. Closing it as a duplicate.
                
> NM Application invalid state transition on reboot command from RM
> -----------------------------------------------------------------
>
>                 Key: YARN-98
>                 URL: https://issues.apache.org/jira/browse/YARN-98
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>            Reporter: Thomas Graves
>            Assignee: Omkar Vinit Joshi
>
> If the RM goes down and comes back up, it tells the NM to reboot.  When the NM reboots,
if it has any applications it aggregates the logs for those applications, then it transitions
the app to APPLICATION_LOG_HANDLING_FINISHED. I saw a case where there was an app that was
in the RUNNING state and tried to transition to APPLICATION_LOG_HANDLING_finished and it got
the invalid transition.
>  [DeletionService #1]2012-04-11 15:12:40,476 WARN org.apache.hadoop.yarn.server.nodemanager.containermanager.application.Application:
Can't handle this event at current state
>  [AsyncDispatcher event handler]org.apache.hadoop.yarn.state.InvalidStateTransitonException:
Invalid event: APPLICATION_LOG_HANDLING_FINISHED at RUNNING
>         at org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:301)
>         at org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:43)
>         at org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:443)
>         at org.apache.hadoop.yarn.server.nodemanager.containermanager.application.ApplicationImpl.handle(ApplicationImpl.java:382)
>         at org.apache.hadoop.yarn.server.nodemanager.containermanager.application.ApplicationImpl.handle(ApplicationImpl.java:58)
>         at org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ApplicationEventDispatcher.handle(ContainerManagerImpl.java:517)
>         at org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl$ApplicationEventDispatcher.handle(ContainerManagerImpl.java:509)
>         at org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:125)
>         at org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:74)
>         at java.lang.Thread.run(Thread.java:619)
> 2012-04-11 15:12:40,476 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.application.Application:
Application application_1333003059741_15999 transitioned from RUNNING to null

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