[ 
https://issues.apache.org/jira/browse/YARN-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702464#comment-13702464
 ] 

Zhijie Shen commented on YARN-296:
----------------------------------

The patch should work, but IMHO, the essential problem is that APP_ACCEPTED is 
not expected at RUNNING. APP_ACCEPTED is created during ScheduleTransition of a 
RMAppAttempt, and is consumed when a RMApp moves from SUBMITTED to ACCEPTED. 
Only after the RMApp enters ACCEPTED, it can further move to RUNNING (similar 
for UnmanagedAM). Therefore, APP_ACCEPTED shouldn't be seen when the RMApp is 
at RUNNING.

Moreover, it seems impossible that APP_ACCEPTED belongs to the last 
RMAppAttempt if the RMApp is retrying, as retry can only happen after the RMApp 
enters ACCEPTED, where APP_ACCEPTED produced by the last RMAppAttempt has 
already be consumed.

[~devaraj], would you mind post more context around the 
InvalidStateTransitonException, such that we can dig more about the problem?
                
> Resource Manager throws InvalidStateTransitonException: Invalid event: 
> APP_ACCEPTED at RUNNING for RMAppImpl
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-296
>                 URL: https://issues.apache.org/jira/browse/YARN-296
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 2.0.2-alpha, 2.0.1-alpha
>            Reporter: Devaraj K
>            Assignee: Mayank Bansal
>         Attachments: YARN-296-trunk-1.patch, YARN-296-trunk-2.patch
>
>
> {code:xml}
> 2012-12-28 11:14:47,671 ERROR 
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Can't handle 
> this event at current state
> org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: 
> APP_ACCEPTED 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.resourcemanager.rmapp.RMAppImpl.handle(RMAppImpl.java:528)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.handle(RMAppImpl.java:72)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationEventDispatcher.handle(ResourceManager.java:405)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationEventDispatcher.handle(ResourceManager.java:389)
>       at 
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:126)
>       at 
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:75)
>       at java.lang.Thread.run(Thread.java:662)
> {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

Reply via email to