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 2026/04/27 15:37:00 UTC

[jira] [Closed] (FLINK-39507) Cluster health check should run on terminal / failed jobs

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

Gyula Fora closed FLINK-39507.
------------------------------
    Fix Version/s: kubernetes-operator-1.15.0
       Resolution: Fixed

merged to main 324663004226b1635ff6248c2e60267ba64e4a57

> Cluster health check should run on terminal / failed jobs
> ---------------------------------------------------------
>
>                 Key: FLINK-39507
>                 URL: https://issues.apache.org/jira/browse/FLINK-39507
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.15.0
>
>
> Currently the cluster / job health check logic is sometimes executed on terminal/failed jobs which can lead to the operator trying to restart these from HA metadata inevitably leading to an unrecoverable failure. 
> We should simply exclude these deployments based on the job status.



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