[
https://issues.apache.org/jira/browse/FLINK-27594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536513#comment-17536513
]
Gyula Fora commented on FLINK-27594:
------------------------------------
Yes, [~thw] what you are saying is part of that. All in all I am working on
hardening and at the same type simplifying the logic with these sanity checks
around HA data.
The ultimate goal is to avoid situations where you accidentally restore from
empty state or a stale savepoint bacause the HA data disappeared for some
reason.
> Only recover JM deployment if HA metadata available
> ---------------------------------------------------
>
> Key: FLINK-27594
> URL: https://issues.apache.org/jira/browse/FLINK-27594
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Priority: Blocker
> Fix For: kubernetes-operator-1.0.0
>
>
> This ticket is related to https://issues.apache.org/jira/browse/FLINK-27572
> The deployment recovery logic for list jobmanager deployments simply performs
> a restoreFromLasteSavepoint operation currently.
> This is incorrect in cases where the HA metadata is not available as it might
> lead to accidentally restoring from an older state.
> We should verify that HA metadata is present and simply perform a
> deployOperation. Once we have this we can actually make the recovery default
> true for all versions.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
