[
https://issues.apache.org/jira/browse/FLINK-30004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise resolved FLINK-30004.
----------------------------------
Fix Version/s: kubernetes-operator-1.3.0
Resolution: Fixed
> Cannot resume deployment after suspend with savepoint due to leftover
> configmaps
> --------------------------------------------------------------------------------
>
> Key: FLINK-30004
> URL: https://issues.apache.org/jira/browse/FLINK-30004
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.2.0
> Reporter: Thomas Weise
> Assignee: Thomas Weise
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.3.0
>
>
> Due to the possibility of incomplete cleanup of HA data in Flink 1.14, the
> deployment can get into a limbo state that requires manual intervention after
> suspend with savepoint. If the config maps are not cleaned up the resumed job
> will be considered finished and the operator recognize the JM deployment as
> missing. Due to check for HA data which are now cleaned up, the job fails to
> start and manual redeployment with initial savepoint is necessary.
> This can be avoided by removing any leftover HA config maps after the job has
> successfully stopped with savepoint (upgrade mode savepoint).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
