drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Parth Chandra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-780) ZooKeeper connection to support configurable cluster id
Date Thu, 29 May 2014 21:41:01 GMT

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

Parth Chandra commented on DRILL-780:
-------------------------------------

The path can be anything. An example would be an enterprise running a zookeeper quorum and
multiple drill clusters corresponding to different user groups registered with zookeeper.
Access to the zookeeper hierarchy would be restricted based on the user group.
For example there could be a sales setup and a marketing setup

sales  drill server root = /sales/drill
marketing drill server root = /mkt/drill
sales drill cluster id = sales-drill-server
marketing drill cluster id = mkt-drill

The zookeeper would have the following hierarchies :

sales/drill/sales-drill-server
mkt/drill/mkt-drill 




> ZooKeeper connection to support configurable cluster id
> -------------------------------------------------------
>
>                 Key: DRILL-780
>                 URL: https://issues.apache.org/jira/browse/DRILL-780
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: George Chow
>
> The cluster-id will have to be configurable and part of the connect string. Default is
drillbit1. If the connection type is local, I will ignore the cluster-id if provided.
>   The connect string URL will be like :
> jdbc:drill:[cluster-id=<clusterid>;]zk=zk1:5181,zk2:5181,zk3:5181  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message