You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2024/02/01 10:20:00 UTC

[jira] [Assigned] (FLINK-34333) Fix FLINK-34007 LeaderElector bug in 1.18

     [ https://issues.apache.org/jira/browse/FLINK-34333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Pohl reassigned FLINK-34333:
-------------------------------------

    Assignee: Matthias Pohl

> Fix FLINK-34007 LeaderElector bug in 1.18
> -----------------------------------------
>
>                 Key: FLINK-34333
>                 URL: https://issues.apache.org/jira/browse/FLINK-34333
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.18.1
>            Reporter: Matthias Pohl
>            Assignee: Matthias Pohl
>            Priority: Blocker
>
> FLINK-34007 revealed a bug in the k8s client v6.6.2 which we're using since Flink 1.18. This issue was fixed with FLINK-34007 for Flink 1.19 which required an update of the k8s client to v6.9.0.
> This Jira issue is about finding a solution in Flink 1.18 for the very same problem FLINK-34007 covered. It's a dedicated Jira issue because we want to unblock the release of 1.19 by resolving FLINK-34007.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)