aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Santhosh Kumar Shanmugham (JIRA)" <>
Subject [jira] [Commented] (AURORA-1946) Make STARTING a transient state
Date Tue, 19 Sep 2017 21:42:00 GMT


Santhosh Kumar Shanmugham commented on AURORA-1946:

Just realized that {{STARTING}} state although can be treated as a Transient state, the timeout
depends on the {{HealthCheckConfig}} which dictates how long the {{Task}} can stay in {{STARTING}}.
Further {{HealthCheckConfig}} is an {{Executor}} concept that the Scheduler does not care
about. So it does not make sense to convert {{STARTING}} into a Transient state that will
degrade into a {{LOST}} state base on a common timeout value.

> Make STARTING a transient state
> -------------------------------
>                 Key: AURORA-1946
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message