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/04/12 14:44:00 UTC

[jira] [Comment Edited] (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=17482344#comment-17482344 ] 

Matthias Pohl edited comment on FLINK-25806 at 4/12/22 2:43 PM:
----------------------------------------------------------------

I linked FLINK-25432 as well: We can remove the ordering of cleanups introduced in FLINK-25432 (see {{{}DefaultResourceCleaner{}}}) as part of removing the legacy high availability services.


was (Author: mapohl):
I linked FLINK-25432 as well: We can remove the ordering of cleanups introduced in FLINK-25432 (see `DefaultResourceCleaner`) as part of removing the legacy high availability services.

> Remove legacy high availability services
> ----------------------------------------
>
>                 Key: FLINK-25806
>                 URL: https://issues.apache.org/jira/browse/FLINK-25806
>             Project: Flink
>          Issue Type: Improvement
>          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.1#820001)