[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112028#comment-17112028
]
Francis Christopher Liu commented on HBASE-11288:
-------------------------------------------------
{quote}
I think we should figure out how this will work. Can be done in parallel in
another issue. Baseline is old clients keep working.
{quote}
Yep let's make backward compatibility work. The simplest would be to just proxy
requests like rest or thrift server does now. If a request for meta hits the
regionserver hosting root. Should be fairly straightforward. Yeah another
branch on top of this one maybe just to not muck things up as we are trying
stuff.
{quote}
The tiering of assignment – root going out before anything else, then all of
the meta regions and then user-space regions. And that ROOT is just so ugly...
the way the rows are done; the crazy comparator.
{quote}
Tiering - yeah this is a tough one since root holds meta locations....it
invariable requires root to be available for writing. What is your concern
here...the complexity of the process?
Ugly root - The way the row keys are done? The nested thing? It's not that bad
at least the logic is being reused. Tho we probably don't need the
"hbase:meta," prefix on all rows....tho I"m not sure what we gain?
{quote}
Currently we have meta and namespace and acls and we still don't get it right
(Duo helped us out here by merging namespace into meta table in master branch).
{quote}
ACLs I've never had an issue with? Namespace AFAIK needed attention and got
kicked around a bit? It's better it's in hbase:meta now...no one will ignore
that table. This is a bit different from tiering assignment issue tho?
{quote}
We should do up a bit of a doc on how this will work; how it will work for old
and new clients (e.g. handing out the whole meta table when client does meta
location lookup); how the proxying will be done so old clients will work when
meta splits, etc.
{quote}
Sounds good. Do you want to brainstorm? Or should I write a proposal then we
work on it?
> 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)
