[FLINK-6078] ZooKeeper based high availability services should not close the underlying CuratorFramework

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.3.0
• Component/s: Runtime / Coordination
• Assignee: Till Rohrmann
• Reporter: Till Rohrmann
• Created: 16/Mar/17 14:50
• Updated: 10/May/17 13:52
• Resolved: 05/May/17 11:49

Description

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.

Issue Links

• duplicates: FLINK-6192 reuse zookeeer client created by CuratorFramework
• is duplicated by: FLINK-6192 reuse zookeeer client created by CuratorFramework
• links to: GitHub Pull Request #3781