[
https://issues.apache.org/jira/browse/HBASE-21943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776353#comment-16776353
]
Hudson commented on HBASE-21943:
--------------------------------
Results for branch branch-2.1
[build #893 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/893/]:
(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.1/893//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/893//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {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/893//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/893//console].
> The usage of RegionLocations.mergeRegionLocations is wrong for async client
> ---------------------------------------------------------------------------
>
> Key: HBASE-21943
> URL: https://issues.apache.org/jira/browse/HBASE-21943
> Project: HBase
> Issue Type: Bug
> Components: asyncclient, Client
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 3.0.0, 2.2.0, 2.0.5, 2.3.0, 2.1.4
>
> Attachments: HBASE-21943-UT-v1.patch, HBASE-21943-UT.patch,
> HBASE-21943-UT.patch, HBASE-21943-v1.patch, HBASE-21943.patch
>
>
> In AsyncRegionLocatorHelper.mergeRegionLocations we create a new
> RegionLocations and call mergeRegionLocations on it, expected that it will be
> changed by this method, but actually the method will not modify the object
> itself, it will return a new one...
> And we are lucky that we create the RegionLocations with the new locations,
> so usually we will get update result. But when testing HBASE-21717, we meet
> another bug in AsyncNonMetaRegionLocator.isEqual, where we missed a '!' when
> checking server name equals...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
