[
https://issues.apache.org/jira/browse/HBASE-24389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119182#comment-17119182
]
Michael Stack commented on HBASE-24389:
---------------------------------------
I had a few quests above [~zhangduo]?
We already have client-side Interfaces -- Registry or RegionLocator. Discussion
of why these put aside?
I hear the bit about not wanting to expose an API that would be hard to
implement in different contexts but the new API is not how we do location query
up to this. New API seems to dictate a Region-at-a-time; will this work if the
RootTable has your 10k entries? What you thinking?
> 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)
