[
https://issues.apache.org/jira/browse/FLINK-34007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810038#comment-17810038
]
Matthias Pohl commented on FLINK-34007:
---------------------------------------
Just checking whether a new instance of \{{LeaderElector}} was created is
tricky because \{{LeaderElector}} is coupled with the k8s backend. We would
either have to mock \{{LeaderElector}} or have to work with some backend.
Anyway, I came up with a quite straight-forward ITCase. I added it to the PR
which is ready to be reviewed now.
> 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)
