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

Posted to dev@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/05/26 15:28:00 UTC

[jira] [Created] (FLINK-27804) Do not observe cluster/job mid upgrade

Gyula Fora created FLINK-27804:
----------------------------------

             Summary: Do not observe cluster/job mid upgrade
                 Key: FLINK-27804
                 URL: https://issues.apache.org/jira/browse/FLINK-27804
             Project: Flink
          Issue Type: Improvement
          Components: Kubernetes Operator
    Affects Versions: kubernetes-operator-1.0.0
            Reporter: Gyula Fora
            Assignee: Gyula Fora


Seems like in some weird cornercases when we observe the FINISHED job (stopped with savepoint) during an upgrade the recorded last snapshot is incorrect (still need to investigate if this is due to a Flink problem or what) This can lead to upgrade errors.

This can be avoided by simply skipping the observe step when the reconciliation status is UPGRADING because at that point we actually know that the job was already shut down and state recorded correctly in the savepoint info.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)