[
https://issues.apache.org/jira/browse/FLINK-27153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537580#comment-17537580
]
Yang Wang commented on FLINK-27153:
-----------------------------------
[~gyfora] I am afraid FLINK-27495 does not fully covered this ticket. Only
checkpoint/savepoint of globally terminal state job will be stored in the
status.
For the savepoint failure and job continuously failing scenarios, the savepoint
upgrade mode still could not work. IIUC, we want to solve this problem in this
ticket at the very begging. But maybe this is not a concrete requirement,
because users could anyway change the upgrade mode to last-state manually if HA
enabled.
> 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
> Assignee: 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.7#820007)
