You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/03/12 09:39:00 UTC

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

    [ https://issues.apache.org/jira/browse/KYLIN-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790386#comment-16790386 ] 

ASF GitHub Bot commented on KYLIN-3865:
---------------------------------------

kyotoYaho commented on pull request #512: KYLIN-3865 Centralize the zookeeper related info
URL: https://github.com/apache/kylin/pull/512
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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