[
https://issues.apache.org/jira/browse/FLINK-26139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498406#comment-17498406
]
Gyula Fora commented on FLINK-26139:
------------------------------------
I think it makes sense to have FAILED/FINISHED/CANCELLED because they actually
differ very significantly from each other.
As for the state machine graph, the operator might be able to recover FAILED
jobs if the user submits a new spec. Not sure what to do with CANCELLED at this
point, that is a bit like SUSPENDED but not fully.
In any case if we use the same enum the user should only be able to set
RUNNING/SUSPENDED as the desired state.
cc [~thw]
> Improve JobStatus tracking and handle different job states
> ----------------------------------------------------------
>
> Key: FLINK-26139
> URL: https://issues.apache.org/jira/browse/FLINK-26139
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Priority: Major
> Attachments: image-2022-02-25-21-22-08-636.png
>
>
> Currently we do not handle any job status changes such as cancellations,
> errors or job completions.
> We should introduce some mechanism to react and deal with these changes and
> expose them in the status as they can potentially affect upgrades.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
