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 2025/07/09 06:24:00 UTC
[jira] [Closed] (FLINK-36212) Failing non-leader JM pod causes the deployment to be stuck in failing state
[ https://issues.apache.org/jira/browse/FLINK-36212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gyula Fora closed FLINK-36212.
------------------------------
Resolution: Fixed
> Failing non-leader JM pod causes the deployment to be stuck in failing state
> ----------------------------------------------------------------------------
>
> Key: FLINK-36212
> URL: https://issues.apache.org/jira/browse/FLINK-36212
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.9.0
> Reporter: Gyula Fora
> Priority: Critical
>
> In case one of the JM replica pods cannot start but otherwise the job is healthy, the operator still cannot recognise the job in a running state.
> This prevents for instance periodic savepoints to be taken or savepoint upgrades to be performed correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)