flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tao Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-6192) reuse zookeeer client created by CuratorFramework
Date Mon, 27 Mar 2017 07:46:41 GMT

     [ https://issues.apache.org/jira/browse/FLINK-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tao Wang updated FLINK-6192:
----------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: FLINK-5839

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

Mime
View raw message