[
https://issues.apache.org/jira/browse/FLINK-34007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808257#comment-17808257
]
Matthias Pohl commented on FLINK-34007:
---------------------------------------
Fair enough. Or we could come up with a Flink-local implementation of the
fabric8io LeaderElector including a possible fix, if a release of the fabric8io
kubernetes client takes too long.
I raised the priority for the issue to Blocker for now. I guess we should get
this one fixed before the 1.19 release. Additionally, I removed the affected
versions 1.17 and 1.16 ([~ZhenqiuHuang] please create another Jira issue if we
have more insights into what's causing the leader election issues in the Flink
1.17-)
> 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)
