[
https://issues.apache.org/jira/browse/HBASE-23055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012505#comment-17012505
]
Duo Zhang commented on HBASE-23055:
-----------------------------------
For the procedure store, it has an interface, so the damage to the whole
architecture can be limited. But meta is another story, and is even more
critical. We reference meta table descriptor everywhere in the code, not sure
if there are other implicit assumptions in the code.
I think we’d better do this on feature branch, do more testing, fix problems,
and then merge it back. I will also help for reviewing and testing the patch,
we’re also very interested in splittable meta, as one of our cluster is already
overloaded on the number of regions...
Thanks.
> Alter hbase:meta
> ----------------
>
> Key: HBASE-23055
> URL: https://issues.apache.org/jira/browse/HBASE-23055
> Project: HBase
> Issue Type: Task
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> hbase:meta is currently hardcoded. Its schema cannot be change.
> This issue is about allowing edits to hbase:meta schema. It will allow our
> being able to set encodings such as the block-with-indexes which will help
> quell CPU usage on host carrying hbase:meta. A dynamic hbase:meta is first
> step on road to being able to split meta.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
