You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/05/10 13:53:04 UTC

[jira] [Resolved] (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 ]

Till Rohrmann resolved FLINK-6192.
----------------------------------
    Resolution: Duplicate

Fixed via FLINK-6078

> 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)