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

Posted to issues@kylin.apache.org by "Zhong Yanghong (JIRA)" <ji...@apache.org> on 2019/03/15 02:21:00 UTC

[jira] [Resolved] (KYLIN-3865) Centralize the zookeeper related info

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

Zhong Yanghong resolved KYLIN-3865.
-----------------------------------
    Resolution: Resolved

> Centralize the zookeeper related info
> -------------------------------------
>
>                 Key: KYLIN-3865
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3865
>             Project: Kylin
>          Issue Type: Improvement
>            Reporter: Zhong Yanghong
>            Assignee: Zhong Yanghong
>            Priority: Major
>             Fix For: v3.0.0
>
>
> Currently zookeeper related infos, like zk path, curator client, are scattered many places, like 
> ZookeeperDistributedLock, DistributedScheduler, CuratorScheduler. It's better to centralize them. There'll be several benefits:
> * Avoid creating multiple curator clients
> * Easy to manage the zk path by leveraging zkChRoot



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)