[
https://issues.apache.org/jira/browse/HBASE-22135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807141#comment-16807141
]
Hudson commented on HBASE-22135:
--------------------------------
Results for branch branch-2
[build #1790 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1790/]:
(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/1790//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/1790//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/1790//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> AsyncAdmin will not refresh master address
> ------------------------------------------
>
> Key: HBASE-22135
> URL: https://issues.apache.org/jira/browse/HBASE-22135
> Project: HBase
> Issue Type: Sub-task
> Components: Admin, asyncclient, Client
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.5
>
> Attachments: HBASE-22135-v1.patch, HBASE-22135.patch
>
>
> This is a big problem... If we stop the active master and promote the backup
> master, all methods in AsyncAdmin, which need to connect the master will fail
> as they try to connect to the old active master forever...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
