You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/10/15 11:41:00 UTC
[jira] [Updated] (FLINK-6192) reuse zookeeer client created by
CuratorFramework
[ https://issues.apache.org/jira/browse/FLINK-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-6192:
----------------------------------
Labels: pull-request-available (was: )
> 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: Deployment / YARN, Runtime / Coordination
> Reporter: Tao Wang
> Assignee: Tao Wang
> Priority: Major
> Labels: pull-request-available
>
> 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
(v8.3.4#803005)