[
https://issues.apache.org/jira/browse/HBASE-24389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118994#comment-17118994
]
Bharath Vissapragada commented on HBASE-24389:
----------------------------------------------
> In general, I think we could move this method to the ClientMetaService but I
> do not think we should lookup this in Registry. As in our deployment, we have
> observer nodes for zk so we do not want to use the MasterRegistry, but we
> still want to spread the loads of accessing root table across multiple
> servers.
Can you please add more detail on this when you get a chance? In your
deployment you'd still face the same issues if you want to load balance the new
ClientMetaService RPCs across masters (if you add/drop masters etc)? or did I
misunderstand you. Thanks
> 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)
