[
https://issues.apache.org/jira/browse/FLINK-27868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550716#comment-17550716
]
Aitozi commented on FLINK-27868:
--------------------------------
I think it will be a good improvement to savepoint with the work of
[https://github.com/apache/flink-kubernetes-operator/pull/255]
One question here: How about the FINISH status will be handled? IMO, the finish
task will not affect the jobs RUNNING status I think (do not have to be reset
to CREATED)
> Harden running job check before triggering savepoints or savepoint upgrades
> ---------------------------------------------------------------------------
>
> Key: FLINK-27868
> URL: https://issues.apache.org/jira/browse/FLINK-27868
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Matyas Orhidi
> Priority: Major
> Fix For: kubernetes-operator-1.1.0
>
>
> Even if the job is in RUNNING state, often not all subtasks are yet running
> which leads to savepoint upgrade / savepoint trigger failures. We should
> harden the isRunning check we use to include subtask states as well.
> This suggestion is desribed more in detail by [~matyas] here:
> https://github.com/apache/flink-kubernetes-operator/pull/237#issuecomment-1137054088
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
