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/10 10:46:00 UTC

[jira] [Assigned] (FLINK-38077) Cancel job upgrades may get stuck indefinitely if JM is missing

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

Gyula Fora reassigned FLINK-38077:
----------------------------------

    Assignee: Gyula Fora

> Cancel job upgrades may get stuck indefinitely if JM is missing
> ---------------------------------------------------------------
>
>                 Key: FLINK-38077
>                 URL: https://issues.apache.org/jira/browse/FLINK-38077
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Critical
>
> Cancel job upgrades (last-state without HA or when we fall back from savepoint) currently can get indefinitely stuck if the JobManager deployment is missing or otherwise the REST API not accessible.
> This is caused by a bug in the "isCancellable" logic that decides that cancel should be used for upgrade or not.



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