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/18 07:06:00 UTC

[jira] [Closed] (FLINK-26140) Add basic handling mechanism to deal with job upgrade errors

     [ https://issues.apache.org/jira/browse/FLINK-26140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora closed FLINK-26140.
------------------------------
    Resolution: Fixed

merged to main: 2204231164bbbe4cfe87e95de54a07290fd95b9f

> 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
>              Labels: pull-request-available
>             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)