You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Matyas Orhidi (Jira)" <ji...@apache.org> on 2022/07/04 07:10:00 UTC

[jira] [Closed] (FLINK-27868) Harden running job check before triggering savepoints or savepoint upgrades

     [ https://issues.apache.org/jira/browse/FLINK-27868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matyas Orhidi closed FLINK-27868.
---------------------------------
    Resolution: Fixed

merged to main via 015b929912479458adfad52e378778f4e6f14163

> 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
>              Labels: pull-request-available
>             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.10#820010)