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 2022/12/06 14:42:00 UTC

[jira] [Commented] (FLINK-25806) Remove legacy high availability services

    [ https://issues.apache.org/jira/browse/FLINK-25806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643901#comment-17643901 ] 

Matthias Pohl commented on FLINK-25806:
---------------------------------------

I guess, we just missed removing these classes. Even though, I don't understand why. We should get rid of them as part of FLINK-26522. [~chesnay] or can you think of any reason why we didn't include them when removing the legacy HAServices.

> Remove legacy high availability services
> ----------------------------------------
>
>                 Key: FLINK-25806
>                 URL: https://issues.apache.org/jira/browse/FLINK-25806
>             Project: Flink
>          Issue Type: Technical Debt
>          Components: Runtime / Coordination
>    Affects Versions: 1.16.0
>            Reporter: Till Rohrmann
>            Assignee: Chesnay Schepler
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.16.0
>
>
> After FLINK-24038, we should consider removing the legacy high availability services {{ZooKeeperHaServices}} and {{KubernetesHaServices}} since they are now subsumed by the multiple component leader election service that only uses a single leader election per component.



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