[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181039#comment-17181039
]
Duo Zhang commented on HBASE-11288:
-----------------------------------
And another thing is what I have said in the past, exposing only a simple
locating API to client will give us more flexibility. For now we will use
master local region because it is easy to implement, but later we could also
change to use a general root table. Client will not see any difference as it
does not care whether you access a master local region or a general table at
master side, just return what the client want is enough. And in HBASE-24765, we
add the ability to return a list of Endpoint to client for getting the
bootstrap information. For now we will return all the master nodes, maybe we
could change it in the future to return a list of region server holding the
root region replicas so we could make use of region servers to distribute the
load.
But if we go with general root table and expose the table interface to client,
it will be hard for us to switch to other solutions in the future. Wire
compatibility is very important even between major releases, and locating root
is one of the necessary step of all client read/write requests.
Thanks.
> Splittable Meta
> ---------------
>
> Key: HBASE-11288
> URL: https://issues.apache.org/jira/browse/HBASE-11288
> Project: HBase
> Issue Type: Umbrella
> Components: meta
> Reporter: Francis Christopher Liu
> Assignee: Francis Christopher Liu
> Priority: Major
> Attachments: jstack20200807_bad_rpc_priority.txt, root_priority.patch
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
