hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars George (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8480) Embed HDFS into HBase
Date Fri, 03 May 2013 06:56:22 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648231#comment-13648231

Lars George commented on HBASE-8480:

[~otis] I agree that this is something that needs to be carefully thought about. But on the
other hand a lot of things have happened since then, HBase and HDFS have seen many optimizations
that makes this more feasible today. Sure, I agree with what [~streamy] commented in the thread,
we will see users overdo it caused by additional overload of the same single or small cluster
setup. But that was always the case.

I believe we need to also compete with the smaller, easier to get going with NoSQL solutions.

But then we also should have a Bootstrap backed website :)
> Embed HDFS into HBase
> ---------------------
>                 Key: HBASE-8480
>                 URL: https://issues.apache.org/jira/browse/HBASE-8480
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Lars George
> HBase is often a bit more involved to get going. We already have the option to host ZooKeeper
for very small clusters. We should have the same for HDFS. The idea is that it adjusts replication
based on the number of nodes, i.e. from 1 to 3 (the default), so that you could start with
a single node and grow the cluster from there. Once the cluster reaches a certain size, and
the admin decides to split the components, we should have a why to export the proper configs/settings
so that you can easily start up an external HDFS and/or ZooKeeper, while updating the HBase
config as well to point to the new "locations".
> The goal is to start a fully operational HBase that can grow from single machine to multi
machine clusters with just a single daemon on each machine.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message