[jira] [Comment Edited] (AURORA-1221) Modify task state machine to treat STARTING as a new active state

["Kai Huang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AURORA-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468426#comment-15468426 ] 

Kai Huang edited comment on AURORA-1221 at 9/6/16 8:27 PM:
-----------------------------------------------------------

There are two side-effects if we add STARTING state into LIVE_STATES thrift constant.

1. aurora job create --wait-until=RUNNING will finish waiting when a task reaches STARTING state (instead of RUNNING)

2. aurora task commands will now also work for STARTING tasks.

For now, we do NOT treat STARTING as live state. It makes more sense to preserve the original meaning of the above two commands, especially for "aurora task ssh", given that the sandbox is being initialized in STARTING state.


was (Author: kaih):
There are two side-effects after we add STARTING state into LIVE_STATES thrift constant.

aurora job create --wait-until=RUNNING will finish waiting when a task reaches STARTING state (instead of RUNNING)

aurora task commands will now also work for STARTING tasks.

> Modify task state machine to treat STARTING as a new active state
> -----------------------------------------------------------------
>
>                 Key: AURORA-1221
>                 URL: https://issues.apache.org/jira/browse/AURORA-1221
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Kai Huang
>
> Scheduler needs to treat STARTING as the new live state. 
> Open: should we treat STARTING as a transient state with general timeout (currently 5 minutes) or treat it as a persistent live state instead?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)