[
https://issues.apache.org/jira/browse/FLINK-27153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17520388#comment-17520388
]
Gyula Fora commented on FLINK-27153:
------------------------------------
Well that was the original idea yes, but I felt that it might make sense to
actually add this behaviour to the `savepoint` upgrade mode instead.
So
upgradeMode = savepoint + kubernetes.operator.job.upgrade.last-state-fallback =
true
would mean that by default we are using the savepoint shutdown, but if anything
happens we dont give an error but use the last checkpoint instead
> 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)
