[ https://issues.apache.org/jira/browse/FLINK-34007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805203#comment-17805203 ]
Zhenqiu Huang commented on FLINK-34007: --------------------------------------- I have been investigating the io.fabric8.kubernetes.client.extended.leaderelection.LeaderElector. Looks like there is a bug in the version 5.12.4, when the leader lose leadership, the loop executor will be shutdown. That is why the leader is not acquired again. Thus, bump the kubernetest-client version will probably help. There is a fix in this PR. https://github.com/fabric8io/kubernetes-client/commit/042c77b360e77dfaac4ae713518b684dcd0d985b > 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: 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)