[
https://issues.apache.org/jira/browse/HBASE-24389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119170#comment-17119170
]
Duo Zhang commented on HBASE-24389:
-----------------------------------
{quote}
So I think my rephrased question would be, is there a plan to load balance
these across masters to avoid hots potting, would be nice to do that in the
follow up patches.
{quote}
See HBASE-24459, I've already opened an issue. The plan is to abstract an
interface at client side which contains two methods, locateMeta and
getAllMetaRegionLocations, and use it in the AsyncMetaTableRegionLocator. The
current implementation is to ask active master, and we could also implement
something like the MasterRegistry to also ask the backup masters, and in our
deployment, we could implement a simple cache server(maybe on k8s) to let
client ask them. I think this is solution we could all be happy.
> Introduce a new master rpc service to locate meta region through root region
> ----------------------------------------------------------------------------
>
> Key: HBASE-24389
> URL: https://issues.apache.org/jira/browse/HBASE-24389
> Project: HBase
> Issue Type: Sub-task
> Components: master, meta
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
>
> And also reimlement the client logic to use the new api to locate meta
> region. In general, this will remove the assumption at client side that there
> is only one meta region.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
