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/03/29 15:54:00 UTC

[jira] [Commented] (FLINK-26916) The Operator ignores job related changes (jar, parallelism) during last-state upgrades

    [ https://issues.apache.org/jira/browse/FLINK-26916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514162#comment-17514162 ] 

Gyula Fora commented on FLINK-26916:
------------------------------------

One way to solve the problem would be to change the current last-state shutdown and restore logic as follows:

SUSPEND
1. Delete deployment
2. Extract last checkpoint pointer from HA configmap -> store in lastSavepoint status

DEPLOY
3. Delete HA configmaps
4. Restore from pointer in lastSavepoint

> The Operator ignores job related changes (jar, parallelism) during last-state upgrades
> --------------------------------------------------------------------------------------
>
>                 Key: FLINK-26916
>                 URL: https://issues.apache.org/jira/browse/FLINK-26916
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-0.1.0, kubernetes-operator-1.0.0
>            Reporter: Matyas Orhidi
>            Priority: Critical
>
> RC: The old jobgraph is being reused when resuming



--
This message was sent by Atlassian Jira
(v8.20.1#820001)