[ https://issues.apache.org/jira/browse/FLINK-34007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805871#comment-17805871 ]
Yang Wang commented on FLINK-34007: ----------------------------------- [~mapohl] Could you please confirm that whether "multi-component leader election" will clean up the leader annotation on the ConfigMap when lost leadership? It seems that the fabric8 Kubernetes client leader elector will not work properly by {{run()}} more than once if we do not clean up the leader annotation. > Flink Job stuck in suspend state after losing leadership in HA Mode > ------------------------------------------------------------------- > > Key: FLINK-34007 > URL: https://issues.apache.org/jira/browse/FLINK-34007 > Project: Flink > Issue Type: Bug > Components: Runtime / Coordination > Affects Versions: 1.16.3, 1.17.2, 1.18.1, 1.18.2 > Reporter: Zhenqiu Huang > Priority: Major > Attachments: Debug.log, job-manager.log > > > The observation is that Job manager goes to suspend state with a failed > container not able to register itself to resource manager after timeout. > JM Log, see attached > -- This message was sent by Atlassian Jira (v8.20.10#820010)