[
https://issues.apache.org/jira/browse/FLINK-27153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17520333#comment-17520333
]
Gyula Fora commented on FLINK-27153:
------------------------------------
[~wangyang0918] previously I felt that if the user sets the
savepointTriggerNonce together with other spec changes, we should first upgrade
then trigger the savepoint.
In any case the semantics of savepointTriggerNonce and the savepoint upgrade
mode is a bit different because one is a cancel with savepoint operation and
the other is a manual savepoint triggering. I feel that the explicit config
option would be clearer to the user
> 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)
