You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/12/19 21:44:00 UTC

[jira] [Updated] (FLINK-30406) Jobmanager Deployment error without HA metadata should not lead to unrecoverable error

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

ASF GitHub Bot updated FLINK-30406:
-----------------------------------
    Labels: pull-request-available  (was: )

> Jobmanager Deployment error without HA metadata should not lead to unrecoverable error
> --------------------------------------------------------------------------------------
>
>                 Key: FLINK-30406
>                 URL: https://issues.apache.org/jira/browse/FLINK-30406
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.4.0
>
>
> Currently we don't have a good way of asserting that the job never started after savepoint upgrade when the JM deployment fails (such as on an incorrect image).
> This easily leads to scenarios which require manual recovery from the user.
> We should try to avoid this with some mechanism to greately improve the robustness of savepoint ugrades.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)