[
https://issues.apache.org/jira/browse/FLINK-11105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714779#comment-16714779
]
Till Rohrmann commented on FLINK-11105:
---------------------------------------
Thanks a lot for creating this issue [~fly_in_gis]. I agree with Tison that
such an {{HighAvailabilityServices}} implementation would be really cool.
Before diving into the implementation, we should first check whether all
currently existing primitives (leader election, leader retrieval, atomic
counter etc.) can be satisfied by etcd. Next we should discuss how to implement
them (mainly which libraries to use) and spend some brain cycles on making a
test plan. This could all go into a design document.
[~yanghua] before we haven't agreed on the details, it does not make sense to
assign this issue to yourself.
> Add a new implementation of the HighAvailabilityServices using etcd
> -------------------------------------------------------------------
>
> Key: FLINK-11105
> URL: https://issues.apache.org/jira/browse/FLINK-11105
> Project: Flink
> Issue Type: New Feature
> Reporter: Yang Wang
> Assignee: vinoyang
> Priority: Major
>
> In flink, we use HighAvailabilityServices to do many things, e.g. RM/JM
> leader election and retrieval. ZooKeeperHaServices is an implementation of
> HighAvailabilityServices using Apache ZooKeeper. It is very easy to integrate
> with hadoop ecosystem. However, the cloud native and micro service are become
> more and more popular. We just need to follow the step and add a new
> implementation EtcdHaService using etcd.
> Now flink has supported to run StandaloneSession on kubernetes and FLINK-9953
> start to make an native integration with kubernetes. If we have the
> EtcdHaService, both of them will benefit from this and we will not have
> deploy a zookeeper service on kubernetes cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
