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/04/09 14:09:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Gyula Fora updated FLINK-27153:
-------------------------------
Description:
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`
was:
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.upgrade.last-state-fallback`
> 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)