[ https://issues.apache.org/jira/browse/AURORA-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172383#comment-16172383 ]
Santhosh Kumar Shanmugham commented on AURORA-1946: --------------------------------------------------- The underlying issue in the above case was that the Task's status updates to {{RUNNING}} and then to {{FAILED}} were never communicated to the Master and eventually to the Scheduler. So the issue lies with the Agent. > Make STARTING a transient state > ------------------------------- > > Key: AURORA-1946 > URL: https://issues.apache.org/jira/browse/AURORA-1946 > Project: Aurora > Issue Type: Task > Reporter: Santhosh Kumar Shanmugham > Assignee: Santhosh Kumar Shanmugham > > We saw a case where an update was stuck in {{IN_PROGRESS}} state, after a > task's status update from {{STARTING}} to {{FAILED}} was lost. In the ideal > scenario the {{Task}} should have been transitioned into {{LOST}} due to a > transient state. But {{STARTING}} is not a transient state. -- This message was sent by Atlassian JIRA (v6.4.14#64029)