[
https://issues.apache.org/jira/browse/HBASE-26790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HBASE-26790:
---------------------------------
Fix Version/s: 2.5.0
2.6.0
3.0.0-alpha-3
2.4.12
> 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: Andrew Kyle Purtell
> Priority: Major
> Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3, 2.4.12
>
>
> 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.1#820001)
