[
https://issues.apache.org/jira/browse/FLINK-26140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517793#comment-17517793
]
Yang Wang commented on FLINK-26140:
-----------------------------------
Introducing the lastStableSpec makes sense to me. Once the job is running
normally more than 30 minutes(configurable value) or having a successful
checkpoint, we will have a lastStableSpec.
> Add basic handling mechanism to deal with job upgrade errors
> ------------------------------------------------------------
>
> Key: FLINK-26140
> URL: https://issues.apache.org/jira/browse/FLINK-26140
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Priority: Major
> Fix For: kubernetes-operator-1.0.0
>
>
> There are various different ways how a stateful job upgrade can fail.
> For example:
> - Failure/timeout during savepoint
> - Incompatible state
> - Corrupted / not-found checkpoint
> - Error after restart
> We should allow some strategies for the user to declare how to handle the
> different error scenarios (such as roll back to earlier state) and what
> should be treated as a fatal error.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
