[jira] [Commented] (FLINK-30437) State incompatibility issue might cause state loss

["Gyula Fora (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-30437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649890#comment-17649890 ] 

Gyula Fora commented on FLINK-30437:
------------------------------------

merged to release-1.3 4e583a0faa0991c61b37ecd9b937fa3e11c6493a

> State incompatibility issue might cause state loss
> --------------------------------------------------
>
>                 Key: FLINK-30437
>                 URL: https://issues.apache.org/jira/browse/FLINK-30437
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.2.0, kubernetes-operator-1.3.0
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.4.0, kubernetes-operator-1.3.1
>
>
> Even though we set:
> execution.shutdown-on-application-finish: false
> execution.submit-failed-job-on-application-error: true
> If there is a state incompatibility the jobmanager marks the Job failed, cleans up HA metada and restarts itself. This is a very concerning behaviour, but we have to fix this on the operator side to at least guarantee no state loss.
> The solution is to harden the HA metadata check properly 



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