[
https://issues.apache.org/jira/browse/FLINK-34007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806699#comment-17806699
]
Matthias Pohl commented on FLINK-34007:
---------------------------------------
If the annotation is the problem, I would assume the issue being somewhere
within the k8s client library. The annotation was never touched by the Flink
code (there's only one read access in
[KubernetesLeaderElector#hasLeadership|https://github.com/apache/flink/blob/c5808b04fdce9ca0b705b6cc7a64666ab6426875/flink-kubernetes/src/main/java/org/apache/flink/kubernetes/kubeclient/resources/KubernetesLeaderElector.java#L115]
to verify the leadership). The lifecycle of the annotation is handled within
the fabric8.io client's \{{LeaderElector}}. I'm gonna do some more
investigation of that code segment. But having more debug k8s/kubernetes-client
logs would help, I guess.
> 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: Debug.log, 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)
