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

Yu Li commented on HBASE-20159:
-------------------------------

We use {{hbase.client.zookeeper.quorum}} to identify the ZK nodes client should 
connect, and if it's not set we will fallback to use {{hbase.zookeeper.quorum}} 
just like before. The setting of {{hbase.client.zookeeper.observer.mode}} only 
takes effect when {{hbase.client.zookeeper.quorum}} is set.

Back to your question, the former setting is correct when client ZK nodes in 
observer mode, while the latter one is a mis-configuration

FWIW, here is a 
[link|http://zookeeper.apache.org/doc/r3.4.6/zookeeperObservers.html] for more 
details about zookeeper observer mode.

> Support using separate ZK quorums for client
> --------------------------------------------
>
>                 Key: HBASE-20159
>                 URL: https://issues.apache.org/jira/browse/HBASE-20159
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Yu Li
>            Assignee: Yu Li
>            Priority: Major
>         Attachments: HBASE-20159.patch, HBASE-20159.v2.patch, 
> HBASE-20159.v3.patch
>
>
> Currently we are using the same zookeeper quorums for client and server, 
> which makes us under risk that if some client connection boost exhausted 
> zookeeper, RegionServer might abort due to zookeeper session loss. Actually 
> we have suffered from this many times in production.
> Here we propose to allow client to use different ZK quorums, through below 
> settings:
> {noformat}
> hbase.client.zookeeper.quorum
> hbase.client.zookeeper.property.clientPort
> hbase.client.zookeeper.observer.mode
> {noformat}
> The first two are for specifying client zookeeper properties, and the third 
> one indicating whether the client ZK nodes are in observer mode. If the 
> client ZK are not observer nodes, HMaster will take responsibility to 
> synchronize necessary meta information (such as meta location and master 
> address, etc.) from server to client ZK



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

Reply via email to