[
https://issues.apache.org/jira/browse/HBASE-24459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159413#comment-17159413
]
Viraj Jasani edited comment on HBASE-24459 at 7/16/20, 7:28 PM:
----------------------------------------------------------------
Thanks [~zhangduo].
{quote}at server side, we will provide caches at backup masters to handle the
requests.
{quote}
This means backup masters will have to talk to active HMaster(through client -
asyncClusterConnection / ZKConnectionRegistry?) to get latest RegionLocations
for meta?
Moreover, cache invalidation for backup masters might be a tricky case.
was (Author: vjasani):
Thanks [~zhangduo].
{quote}at server side, we will provide caches at backup masters to handle the
requests.
{quote}
This means backup masters will have to talk to active HMaster(through client /
ZKConnectionRegistry?) to get latest RegionLocations for meta since we can't
get that detail from ZK anymore?
> Move the locateMeta logic from AsyncMetaRegionTableLocator to
> ConnectionRegistry
> --------------------------------------------------------------------------------
>
> Key: HBASE-24459
> URL: https://issues.apache.org/jira/browse/HBASE-24459
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Priority: Major
>
> Now the related code is only in AsyncMetaRegionTableLocator, we could make
> the actually implementation pluggable, so we do not always need to go to the
> active master.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
