[
https://issues.apache.org/jira/browse/HBASE-8480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648173#comment-13648173
]
stack commented on HBASE-8480:
------------------------------
/me I love when fellows quote the mailing list and the mailing list was good
[~larsgeorge] So, we have minihbase which has everything in the one jvm. And
then we have pseudo-distributed w/ all daemons on the one node... then we have
full-blown cluster. How you want to bridge between these stages? How you
think it would work? We'd always write dfs, never local fs? To go from
standalone hbase, we'd allow a dn from another host join the cluster? How
would we pass off Namenode responsibilities to a real namenode?
I like the idea of bundling the master and regionserver in one binary better;
no more special master treatment... any one can be msster and or a
regionserver? That seems easier and would do a bunch of simplification? Would
even help your project here?
Thanks boss.
> 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
