[
https://issues.apache.org/jira/browse/HBASE-20159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413490#comment-16413490
]
Yu Li commented on HBASE-20159:
-------------------------------
{quote}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
on project hbase-thrift: Failed to install metadata
org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
parse metadata
/home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
in epilog non whitespace content is not allowed but got / (position: END_TAG
seen ...</metadata>\n/... @25:2) -> [Help 1]
{quote}
The hadoopcheck error looks strange and I cannot reproduce in local. Not sure
whether any JIRA tracking this although seems irrelative to this one.
> 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
>
>
> 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)