[ https://issues.apache.org/jira/browse/HBASE-26790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558727#comment-17558727 ]
Hudson commented on HBASE-26790: -------------------------------- Results for branch branch-2 [build #576 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/576/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (x) {color:red}-1 general checks{color} -- For more information [see general report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/576/General_20Nightly_20Build_20Report/] (x) {color:red}-1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/576/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/] (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-2/576/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/] (x) {color:red}-1 jdk11 hadoop3 checks{color} -- For more information [see jdk11 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/576/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/] (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://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/576//console]. > getAllRegionLocations can cache locations with null hostname > ------------------------------------------------------------ > > Key: HBASE-26790 > URL: https://issues.apache.org/jira/browse/HBASE-26790 > Project: HBase > Issue Type: Bug > Reporter: Bryan Beaudreault > Assignee: Bryan Beaudreault > Priority: Major > Fix For: 2.5.1, 3.0.0-alpha-4, 2.4.14 > > > RegionLocator methods typically delegate to > ConnectionImplementation.locateRegion, which throws a > NoServerForRegionException if the located region's serverName is null. > RegionLocator.getAllRegionLocations does not go through that path, instead > caching all returned region locations without any validation. This can result > in a "dirty" meta cache, since clients do not expect to have null serverNames > in the meta cache. We should add the same throwing of > NoServerForRegionException to this method as used in the others. Or at least > we should not cache the result if the serverName is null. -- This message was sent by Atlassian Jira (v8.20.7#820007)