[ https://issues.apache.org/jira/browse/FLINK-34007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809858#comment-17809858 ]
Yang Wang commented on FLINK-34007: ----------------------------------- It seems that the fabric8 K8s client community leans towards to make the {{LeaderElector}} non-restartable. And using a same lock identity should also work for us when creating a new leader-elector instance. So your PR looks good to me. About the test: We just need to have a test to guard that a new leader-elector instance should be created instead of reusing the existing one. Right? > 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.19.0, 1.18.1, 1.18.2 > Reporter: Zhenqiu Huang > Priority: Blocker > Labels: pull-request-available > Attachments: Debug.log, LeaderElector-Debug.json, 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)