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 2022/12/29 13:00:00 UTC

[jira] [Assigned] (FLINK-30528) Job may be stuck in upgrade loop when last-state fallback is disabled and deployment is missing

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

Gyula Fora reassigned FLINK-30528:
----------------------------------

    Assignee: Gyula Fora

> Job may be stuck in upgrade loop when last-state fallback is disabled and deployment is missing
> -----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-30528
>                 URL: https://issues.apache.org/jira/browse/FLINK-30528
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.3.0
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Major
>
> When last-state upgrade fallback is disabled (or we are switching flink versions) and the JM deployment is missing for some reason, we get stuck in the upgrade loop as the spec change /upgrade logic always takes precedence over the JM deployment recovery logic.
> In this cases the JM deployment need to be recovered first so savepoint upgrade can be executed.



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