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

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2023/03/01 08:14:00 UTC

[jira] [Created] (FLINK-31277) JM Deployment recovery logic inconsistent with health related restart

Gyula Fora created FLINK-31277:
----------------------------------

             Summary: JM Deployment recovery logic inconsistent with health related restart 
                 Key: FLINK-31277
                 URL: https://issues.apache.org/jira/browse/FLINK-31277
             Project: Flink
          Issue Type: Bug
          Components: Kubernetes Operator
    Affects Versions: kubernetes-operator-1.4.0
            Reporter: Gyula Fora
            Assignee: Gyula Fora
             Fix For: kubernetes-operator-1.5.0


The current JM Deployment logic that restarts missing deployments strictly requires HA metadata event for stateless deployments.

This is inconsistent with how the cluster health check related restarts work which can cause the operator to delete an unhealthy deployment and potentially leave it missing if the first deploy attempt fails.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)