You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2022/03/18 07:35:00 UTC

[jira] [Comment Edited] (FLINK-26577) Avoid state loss when switching to last-state upgrade mode

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

Yang Wang edited comment on FLINK-26577 at 3/18/22, 7:34 AM:
-------------------------------------------------------------

I am just thinking what we promise to the users. I lean to not allow switching to last-state if the HA is not enabled previously.


was (Author: fly_in_gis):
I am just thinking what we promise to the users. I lean to not allow switching to last-state if the HA is not enabled previously. And I believe we have this behavior before FLINK-26367.

> Avoid state loss when switching to last-state upgrade mode
> ----------------------------------------------------------
>
>                 Key: FLINK-26577
>                 URL: https://issues.apache.org/jira/browse/FLINK-26577
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Priority: Major
>
> At the moment there are several corner cases which can lead to accidental state loss (or at least weird behaviour) when switching to last-state upgrade mode from other modes.
> 2 cases that immediately come to mind:
> savepoint to last-state: 
> When the new upgrade mode is last-state, the job deployment will simply be deleted. If HA was not enabled previously, the last savepoint might be very far back in time. 
> stateless to last-state:
> If checkpointing and HA is not enabled, the deployment will simply be killed like previously and we might start a job from empty state. Maybe taking a savepoint would be the right approach in this case and continue from there.
> Maybe when switching between modes we should consider the previous mode as well as the target mode when deciding the on the suspend strategy. We could also simply not allow to switch to last-state if HA is not enabled previously but that might be too restrictive.



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