[
https://issues.apache.org/jira/browse/FLINK-34007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808441#comment-17808441
]
Yang Wang commented on FLINK-34007:
-----------------------------------
I also remember that the fabric8 kubernetes-client community has a very good
response. If the {{LeaderElector}} is designed for only run once, though I do
not think this is the reasonable behavior, then we need to create a new
{{LeaderElector}} when lost leadership.
For option #3, it might be unnecessary because {{LeaderElector}} could work as
expected when creating a new instance with same lock identity. It is a larger
effort to do such refactor without additional benefits.
BTW, maybe I miss some background. [~gyfora] Could you please share me why we
need to change the thread pool to 3 in {{{}KubernetesLeaderElector{}}}?
> 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)
