[FLINK-6192] reuse zookeeer client created by CuratorFramework

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: Deployment / YARN, Runtime / Coordination
• Labels: pull-request-available
• Assignee: Tao Wang
• Reporter: Tao Wang
• Created: 27/Mar/17 07:34
• Updated: 15/Oct/19 11:40
• Resolved: 10/May/17 13:52

Description

Now in yarn mode, there're three places using zookeeper client(web monitor, jobmanager and resourcemanager) in ApplicationMaster/JobManager, while there're two in TaskManager. They create new one zookeeper client when they need them.

I believe there're more other places do the same thing, but in one JVM, one CuratorFramework is enough for connections to one zookeeper client, so we need a singleton to reuse them.

Issue Links

• duplicates: FLINK-6078 ZooKeeper based high availability services should not close the underlying CuratorFramework
• is duplicated by: FLINK-6078 ZooKeeper based high availability services should not close the underlying CuratorFramework
• links to: GitHub Pull Request #3617
• links to: GitHub Pull Request #3617