[
https://issues.apache.org/jira/browse/HBASE-21658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839064#comment-16839064
]
Hudson commented on HBASE-21658:
--------------------------------
Results for branch branch-2.1
[build #1139 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1139/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1139//console].
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1139//console].
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1139//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Should get the meta replica number from zk instead of config at client side
> ---------------------------------------------------------------------------
>
> Key: HBASE-21658
> URL: https://issues.apache.org/jira/browse/HBASE-21658
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.5
>
> Attachments: HBASE-21658-addendum.patch
>
>
> For now, the ZKAsyncRegistry will use the znodePaths.metaReplicaZNodes for
> getting meta replicas. But actually, this config should only be used by
> HMaster. At client side, we should list the zk directory to get all the
> available meta replicas.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)