[ https://issues.apache.org/jira/browse/TEZ-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491867#comment-14491867 ]
Jeff Zhang commented on TEZ-2304: --------------------------------- [~jlowe] Could you attach the full app logs ? Initial doubt is that the attemptId may be set incorrectly. {code} 2015-04-09 20:05:42,055 INFO [AsyncDispatcher event handler] impl.TaskAttemptImpl: attempt_1428329756093_168563_1_00_006728_1 TaskAttempt Transitioned from NEW to KILLED due to event TA_RECOVER 2015-04-09 20:05:45,748 INFO [AsyncDispatcher event handler] impl.TaskAttemptImpl: attempt_1428329756093_168563_1_00_006728_1 TaskAttempt Transitioned from NEW to START_WAIT due to event TA_SCHEDULE {code} > InvalidStateTransitonException TA_SCHEDULE at START_WAIT during recovery > ------------------------------------------------------------------------ > > Key: TEZ-2304 > URL: https://issues.apache.org/jira/browse/TEZ-2304 > Project: Apache Tez > Issue Type: Bug > Affects Versions: 0.6.0 > Reporter: Jason Lowe > > I saw a Tez AM throw a few InvalidStateTransitonException (sic) instances > during recovery complaining about TA_SCHEDULE arriving at the START_WAIT > state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)