[
https://issues.apache.org/jira/browse/HBASE-26790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault updated HBASE-26790:
--------------------------------------
Fix Version/s: 2.5.1
2.4.14
(was: 2.6.0)
Release Note: getAllRegionLocations will no longer add locations to the
MetaCache which have no server name. Region locations without a server name can
occur for brief periods during region splits and merges, but the MetaCache
relies on every cached location having a server name.
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to master and branch-2*.
Thanks for the review [~apurtell]!
> 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
> Labels: patch-available
> 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)
