[ https://issues.apache.org/jira/browse/YARN-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266480#comment-16266480 ]
lujie edited comment on YARN-6948 at 11/27/17 8:11 AM: ------------------------------------------------------- Hi: Recently I restudy this bug, and find the bug reason !yarn-6948.png! When the applicationAttempt performs AttemptstartedTransition, it will send AppAttemptAddedSchedulerEvent to CapacityScheduler and transform to SUBMITTED, then the CapacityScheduler will send ATTEMPT_ADDED back to applicationAttempt, But if client send kill command to applicationAttempt, applicationAttempt will transform to FINAL_SAVING , and if ATTEMPT_ADDED arrives before applicationAttempt chang its state from FINAL_SAVING to KILLED, applicationAttempt will throw InvalidStateTransitonException exception. it will be ok if ATTEMPT_ADDED arrives at KILLED(ignore the event) or SUBMITTED was (Author: xiaoheipangzi): Hi: Recently I restudy this bug, and find the bug reason !yarn-6948.png! When the applicationAttempt performs AttemptstartedTransition, it will send AppAttemptAddedSchedulerEvent to CapacityScheduler and transform to SUBMITTED, then the CapacityScheduler will send ATTEMPT_ADDED back to applicationAttempt, But if client send kill command to applicationAttempt, applicationAttempt will transform to FINAL_SAVING , and if ATTEMPT_ADDED arrives before applicationAttempt chang its state from FINAL_SAVING to KILLED, applicationAttempt will throw InvalidStateTransitonException exception. it will be ok if ATTEMPT_ADDED arrives at KILLED or SUBMITTED > Invalid event: ATTEMPT_ADDED at FINAL_SAVING > -------------------------------------------- > > Key: YARN-6948 > URL: https://issues.apache.org/jira/browse/YARN-6948 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn > Affects Versions: 2.8.0 > Reporter: lujie > Attachments: yarn-6948.png > > > When I send kill command to a running job, I check the logs and find the > Exception: > {code:java} > 2017-08-03 01:35:20,485 ERROR > org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: > Can't handle this event at current state > org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: > ATTEMPT_ADDED at FINAL_SAVING > 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.resourcemanager.rmapp.attempt.RMAppAttemptImpl.handle(RMAppAttemptImpl.java:757) > at > org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl.handle(RMAppAttemptImpl.java:106) > at > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationAttemptEventDispatcher.handle(ResourceManager.java:834) > at > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationAttemptEventDispatcher.handle(ResourceManager.java:815) > at > org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:173) > at > org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:106) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org