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/02 08:43:00 UTC

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

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

Gyula Fora closed FLINK-31277.
------------------------------
    Resolution: Fixed

Merged to main 8a30e9bd770b32e28d2a7c0fe1830f5f6d9ab090

> 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
>            Priority: Major
>              Labels: pull-request-available
>             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)