[ https://issues.apache.org/jira/browse/HBASE-20159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Drob reopened HBASE-20159: ------------------------------- > 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.branch-2.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)