[
https://issues.apache.org/jira/browse/HBASE-28521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843063#comment-17843063
]
Hudson commented on HBASE-28521:
--------------------------------
Results for branch branch-3
[build #198 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/198/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/198/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/198/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/198/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Use standard ConnectionRegistry and Client API to get region server list in
> in replication
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-28521
> URL: https://issues.apache.org/jira/browse/HBASE-28521
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> This is for allowing specify cluster key without zookeeper in replication
> peer config.
> For now, we will set a watcher on zookeeper for fetching the region server
> list for the remote cluster, this means we must know the zookeeper address of
> the remote cluster. This should be fixed as we do not want to leak the
> zookeeper outside the cluster itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
