[
https://issues.apache.org/jira/browse/HBASE-24389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119096#comment-17119096
]
Bharath Vissapragada commented on HBASE-24389:
----------------------------------------------
I think I see what you mean. I didn't realize you put up a patch for this
already. I skimmed through it, you implemented a new meta lookup (outside of
what registry provides) based on your root implementation that always goes
through the active master sub (which is picked up from registry). 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.
> 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)
