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/12 13:06:00 UTC

[jira] [Created] (FLINK-27594) Only recover JM deployment if HA metadata available

Gyula Fora created FLINK-27594:
----------------------------------

             Summary: Only recover JM deployment if HA metadata available
                 Key: FLINK-27594
                 URL: https://issues.apache.org/jira/browse/FLINK-27594
             Project: Flink
          Issue Type: Bug
          Components: Kubernetes Operator
            Reporter: Gyula Fora
             Fix For: kubernetes-operator-1.0.0


This ticket is related to https://issues.apache.org/jira/browse/FLINK-27572

The deployment recovery logic for list jobmanager deployments simply performs a restoreFromLasteSavepoint operation currently.

This is incorrect in cases where the HA metadata is not available as it might lead to accidentally restoring from an older state.

We should verify that HA metadata is present and simply perform a deployOperation. Once we have this we can actually make the recovery default true for all versions.



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