[
https://issues.apache.org/jira/browse/HBASE-11165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121455#comment-14121455
]
stack commented on HBASE-11165:
-------------------------------
[~mantonov]
bq. ...that's kind of hard to compare the relative complexity without proposed
detailed designs for both
Hopefully we don't need detailed design. I think a sketch will be sufficient.
TODO.
[~eclark]
bq. ....Then we should be focusing there on places where we have slowness.
'slowness' is but one of the dimensions that needs addressing. There is also
'size' -- size in HDFS, size of cache -- as well as availability
No to federation. I don't think we need to split master.
Is the failure you refer to our having a root and not making use of it?
Let me post something for folks to skewer (listing tangible benefit)..
Hopefully tonight (out for the day).
Good stuff
> 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)
