[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155220#comment-17155220
]
Duo Zhang commented on HBASE-11288:
-----------------------------------
{quote}
I didn't remove it. Caching for ROOT migrated further down the doc. to its own
section. ROOT caching does not seem particular to any one of the two
suggestions for ROOT location; with simple location API for hbase:meta Regions
in ConnectionRegistry API, plugging in a ROOT cache tier seems doable in either
case. Thanks.
{quote}
I'm a bit confused. You mean that, with 'general root table', we will also only
expose a very simple API for locating meta? Then why do we still need a
'general root table'? And how do you plan to only expose a simple locating API
on top of a 'general root table'? Client will not go to the root region
directly but the cache on master and backup master?
If we go with this direction, why do we need a 'general root table'? All the 3
advantages listed in the design doc are completely gone. Comparing to 'master
local region', it only has a disadvantage that it needs 2-tier.
So if you both think the caching should work like this, then the discussion is
over. I do not see any advantages of 'general root table' then. Let's just go
with 'master local region'.
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
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
