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 01:36:01 GMT

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

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

To support this change we are changing the connect string format.  Note that the cluster id
is not sufficient, the client needs to accept the path to the drill root in zookeeper as well.
This path and cluster id will now be appended to the end of the connect string.
In addition, the jdbc:drill prefix seems odd and will be removed.

Final canonical form of the connect string:

zk=zk1:port[,,zk2:p2,...][/<path_to_drill_root>/<cluster_id>]"
examples:
        zk=localhost:2181
        zk=localhost:2181/drill/drillbits1
        zk=localhost:2181,zk2:2181/drill/drillbits1

The connect string to connect directly to a drillbit :
local=host:port
example:
        local=127.0.0.1:31010



> 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