Improve state management at Program level and RunRecord level

Description

States for Program level is different from Run level this causes discrepancy in certain scenarios.

Program level states: STARTING, RUNNING, STOPPED,
Run-record level: RUNNING, SUSPENDED, COMPLETED, FAILED, KILLED

We should take a pass at this state management and reconcile the difference between the program and run-record level.

Release Notes

None

Activity

Show:
Bhooshan Mogal
November 2, 2015, 9:10 PM

This is a related ticket that was opened a while ago, and has a lot more details.

Terence Yim
November 2, 2015, 7:53 PM

The REST call should only consult the RunRecord table, not the ProgramRuntimeService. It'll be good to add `STARTING` state to the RunRecord table as well.

Won't Fix

Assignee

Terence Yim

Reporter

Sreevatsan Raman