[
https://issues.apache.org/jira/browse/HBASE-23275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047035#comment-17047035
]
Hudson commented on HBASE-23275:
--------------------------------
Results for branch branch-2
[build #2514 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2514/]:
(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/branch-2/2514//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/branch-2/2514//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/branch-2/2514//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Track active master server name in ActiveMasterManager
> ------------------------------------------------------
>
> Key: HBASE-23275
> URL: https://issues.apache.org/jira/browse/HBASE-23275
> Project: HBase
> Issue Type: Sub-task
> Components: master
> Affects Versions: 3.0.0
> Reporter: Bharath Vissapragada
> Assignee: Bharath Vissapragada
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> We already track whether the cluster has an active master, it is just another
> RPC to the zookeeper to fetch the active master's hostname. Tracking it helps
> load balance client requests to fetch the active master information.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
