[
https://issues.apache.org/jira/browse/HBASE-24459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146657#comment-17146657
]
Michael Stack edited comment on HBASE-24459 at 6/26/20, 10:03 PM:
------------------------------------------------------------------
Duo has talked of keeping the ConnectionRegistry Interface read-only and simple
so Implemention could go against an existing caching tier.
Could also keep the cache tier in-cluster with Master farming out location
updates on (rare) change via remote procedure infrastructure so any
RegionServer can participate? Or simpler, ROOT Table Region replication across
all Masters; active and backups.
For implementation later.
was (Author: stack):
Duo has talked of keeping the ConnectionRegistry Interface read-only and simple
so Implemention could go against an existing caching tier.
Could also keep the cache tier in-cluster with Master farming out location
updates on (rare) change via remote procedure infrastructure so any
RegionServer can participate?
For implementation later.
> 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)
