[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176644#comment-17176644
]
Duo Zhang commented on HBASE-11288:
-----------------------------------
But you still do not answer my question directly right? Why root must be a
table?
In my implementation, root is still stored as a ‘region’, so we could still
reuse most of the code right? And I’ve done a refactoring on master for
generalizing a CatalogFamilyFormat, for putting these methods. And now we
already have a framework to distributed the load of root, so there is no such
‘specialized solution’, we just use an existing solution, for distributed
‘cluster bootstrap information’.
Passing ITBLL is good, even without splitting support, this means our proc-v2
framework is stable enough after the several years polishing, to support
complicated logic, and introducing root table is generally fine. Though I still
do not like that we introduce a lot of new state in SCP. It is easy to add new
states but hard to delete them.
But I’m very disappointed that, starting from the first comment, you never
changed anything. Though I explained a lot, you just did not see and kept
saying root as table is the only good way, all other ways are compromise. You
just kept pushing your solution, I do not think this is a good way for
collaboration.
> 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)
