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/04/11 09:10:00 UTC

[jira] [Comment Edited] (FLINK-27153) Allow optional last-state fallback for savepoint upgrade mode

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

Yang Wang edited comment on FLINK-27153 at 4/11/22 9:09 AM:
------------------------------------------------------------

{code:java}
operator.job.upgrade.savepoint.last-state-fallback: false
operator.job.upgrade.last-state.savepoint-if-running: false{code}
 

Having above two config options makes sense to me. Or maybe you could have better name for them :)


was (Author: fly_in_gis):
{code:java}
operator.job.upgrade.savepoint.last-state-fallback
operator.job.upgrade.last-state.savepoint-if-running {code}
 

Having above two config options makes sense to me. Or maybe you could have better name for them :)

> Allow optional last-state fallback for savepoint upgrade mode
> -------------------------------------------------------------
>
>                 Key: FLINK-27153
>                 URL: https://issues.apache.org/jira/browse/FLINK-27153
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Priority: Major
>             Fix For: kubernetes-operator-1.0.0
>
>
> In many cases users would prefer to take a savepoint if the job is healthy before performing an upgrade but still allow checkpoint based (last-state) recovery in case the savepoint fails or the job is generally in a bad state.
> We should add a configuration flag for this that the user can set in the flinkConfiguration:
> `kubernetes.operator.job.upgrade.last-state-fallback`



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