[
https://issues.apache.org/jira/browse/TEZ-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560187#comment-14560187
]
Jeff Zhang commented on TEZ-2304:
---------------------------------
bq. Maybe createAttempt could be changed to use the last seen attempt id
instead?
This should also solve this issue. But I think it would be better to recover
the task attempt even if it has not started (log TaskAttemptFinishedEvent even
if there's no TaskAttemptStartedEvent), otherwise we may get wrong
killedTaskAttemptCount, although it is not critical. And I believe recovery
should recover AM to the same state of last application attempt.
> 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
> Labels: Recovery
> Attachments: 168563_recovery.gz
>
>
> 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)
