[ https://issues.apache.org/jira/browse/HBASE-20159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421305#comment-16421305 ]
Hudson commented on HBASE-20159: -------------------------------- Results for branch master [build #279 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/279/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/master/279//General_Nightly_Build_Report/] (x) {color:red}-1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/master/279//JDK8_Nightly_Build_Report_(Hadoop2)/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/master/279//JDK8_Nightly_Build_Report_(Hadoop3)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. > 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 > Components: Client, Operability, Zookeeper > Reporter: Yu Li > Assignee: Yu Li > Priority: Major > Fix For: 3.0.0, 2.1.0 > > Attachments: 20159.addendum, 20159.addendum2.patch, > 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)