You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/12/29 14:52:00 UTC

[jira] [Updated] (FLINK-30527) Last-state suspend followed by flinkVersion change may lead to state loss

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

ASF GitHub Bot updated FLINK-30527:
-----------------------------------
    Labels: pull-request-available  (was: )

> Last-state suspend followed by flinkVersion change may lead to state loss
> -------------------------------------------------------------------------
>
>                 Key: FLINK-30527
>                 URL: https://issues.apache.org/jira/browse/FLINK-30527
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.2.0, kubernetes-operator-1.3.0
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Critical
>              Labels: pull-request-available
>
> We do not check flink version changes on recovery, so if the user suspended the job using last-state mode (or that was the only mode available) and then subsequently the flinkVersion is changed to a non-HA compatible version, the job would be restored using last-state and state would be lost.
> In these cases we should set an error in the Flink resource instructing the user that changing version is not allowed at that point.



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