Till Rohrmann created FLINK-6078:
------------------------------------
Summary: ZooKeeper based high availability services should not
close the underlying CuratorFramework
Key: FLINK-6078
URL: https://issues.apache.org/jira/browse/FLINK-6078
Project: Flink
Issue Type: Bug
Components: Distributed Coordination
Affects Versions: 1.3.0
Reporter: Till Rohrmann
Assignee: Till Rohrmann
Fix For: 1.3.0
ZooKeeper based high availability tools like
{{ZooKeeperLeaderRetrievalService}} and {{ZooKeeperLeaderElectionService}}
expect that every instance of the services have a dedicated
{{CuratorFramework}} instance assigned. Thus, they also close this
{{CuratorFramework}} when the service is closed. This does not play well along
with the newly introduced {{HighAvailabilityServices}} which caches a single
{{CuratorFramework}} and shares it among all created services. In order to make
it work properly together I propose to change the behaviour such that we no
longer close the {{CuratorFramework}} clients in the ZooKeeper based services.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
