[
https://issues.apache.org/jira/browse/FLINK-34007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Pohl resolved FLINK-34007.
-----------------------------------
Resolution: Fixed
* master
**
[79cccd7103a304bfa07104dcafd1f65a032c88ce|https://github.com/apache/flink/commit/79cccd7103a304bfa07104dcafd1f65a032c88ce]
**
[95417a4857ec87a349c0fa9f4d3951f7d3807844|https://github.com/apache/flink/commit/95417a4857ec87a349c0fa9f4d3951f7d3807844]
**
[927972ff4ad6252fd933fcc627c7d95dbbdae431|https://github.com/apache/flink/commit/927972ff4ad6252fd933fcc627c7d95dbbdae431]
> 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
> Assignee: Matthias Pohl
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.19.0
>
> 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)
