You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2022/09/23 18:35:00 UTC

[jira] [Commented] (HBASE-26790) getAllRegionLocations can cache locations with null hostname

    [ https://issues.apache.org/jira/browse/HBASE-26790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608882#comment-17608882 ] 

Bryan Beaudreault commented on HBASE-26790:
-------------------------------------------

Seems this actually landed in 2.5.0. Fixed Fix Versions

> 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.0, 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.10#820010)