[jira] [Comment Edited] (HBASE-11288) Splittable Meta

["Michael Stack (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110755#comment-17110755 ] 

Michael Stack edited comment on HBASE-11288 at 5/19/20, 1:20 AM:
-----------------------------------------------------------------

<fantasy>
Can we split meta in a way such that older clients keep working? Perhaps old clients get a proxying Region that fields requests to the actual split meta table so they keep working?

Can we NOT do a ROOT table w/ its crazy meta-meta comparator?
</fantasy>

Yeah, when registry is hosted by Master, master now carries some location ops we used farm out to zk. Master-hosted registry could host Meta table Region locations too... seems apt for a Registry. We've not been good at tier's of assign; i.e. ROOT first, then META regions.


was (Author: stack):
<fantasy>
Can we split meta in a way such that older clients keep working? Perhaps old clients get a proxying Region that fields requests to the actual split meta table so they keep working?

Can we NOT do a ROOT table w/ its crazy meta-meta comparator?
</fantasy>

Yeah, when registry is hosted by Master, master now carries some location ops we used farm out to zk. Master-hosted registry could host Meta table Region locations too... seems apt for a Registry.

> 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
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)