[
https://issues.apache.org/jira/browse/HBASE-11165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999672#comment-13999672
]
Mikhail Antonov commented on HBASE-11165:
-----------------------------------------
I think the numbers mentioned for the particular usecase were somewhat like
region size around 80gb being an issue.
bq. We should also discuss why few, large regions are bad
I'd think that one of limitations of overly big regions (besides
one-mapper-per-region) is that they're inconvenient to split/move
around/compact?
bq. Now, maybe only a few regions are being written, in that case we need much
less heap for the memstores.
Do you think that having an option to share memstore between group of regions
(rather than having many small, like 64mb or 32mb, memstores) would help here?
> 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
>
> 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.2#6252)
