[
https://issues.apache.org/jira/browse/FLINK-30528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora closed FLINK-30528.
------------------------------
Fix Version/s: kubernetes-operator-1.4.0
kubernetes-operator-1.3.1
Resolution: Fixed
release-1.3 c4e691696086358dfa981e35d9a799e7f31b1784
main a1842d4c0170feb008293963ec51c0343f42771d
> 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
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.4.0, kubernetes-operator-1.3.1
>
>
> 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)
