[
https://issues.apache.org/jira/browse/HBASE-11165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137783#comment-14137783
]
Andrey Stepachev commented on HBASE-11165:
------------------------------------------
Looks like we can do two things to solve that on up to 1.0 version of hbase
(without significant changes)
1. Meta should keep 1 version (with atomic row updates we definitely need no
more then one actual version), even better make that configurable.
2. Meta HLogs should be archived for debugging
That will reduce scan overhead (much less KVs to scan) and reduce memory
footprint and reduce load times for very big metas.
[~virag], [~apurtell], do we have significant objections on that?
> Scaling so cluster can host 1M regions and beyond (50M regions?)
> ----------------------------------------------------------------
>
> Key: HBASE-11165
> URL: https://issues.apache.org/jira/browse/HBASE-11165
> Project: HBase
> Issue Type: Brainstorming
> Reporter: stack
> Attachments: HBASE-11165.zip, Region Scalability test.pdf,
> zk_less_assignment_comparison_2.pdf
>
>
> This discussion issue comes out of "Co-locate Meta And Master HBASE-10569"
> and comments on the doc posted there.
> A user -- our Francis Liu -- needs to be able to scale a cluster to do 1M
> regions maybe even 50M later. This issue is about discussing how we will do
> that (or if not 50M on a cluster, how otherwise we can attain same end).
> More detail to follow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
