[
https://issues.apache.org/jira/browse/FLINK-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002695#comment-16002695
]
ASF GitHub Bot commented on FLINK-6192:
---------------------------------------
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3617
@WangTaoTheTonic it looks like this PR can now be closed.
> reuse zookeeer client created by CuratorFramework
> -------------------------------------------------
>
> Key: FLINK-6192
> URL: https://issues.apache.org/jira/browse/FLINK-6192
> Project: Flink
> Issue Type: Sub-task
> Components: JobManager, YARN
> Reporter: Tao Wang
> Assignee: Tao Wang
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
