hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ken Weiner <...@gumgum.com>
Subject Re: Smallest production HBase cluster
Date Fri, 23 Jul 2010 16:53:42 GMT

We have a small cluster (0.20.4 currently) serving real time requests, 1
Master/NameNode/ZK and 3 RegionServers/DataNode on EC2. All nodes are
currently m1.large.  We realize that we are way underpowered compared to
most recommendations.  We plan to add nodes and likely increase the power of
each node as our HBase usage grows which is easy to do on EC2.  Our cluster
has been running smoothly for the most part.  We did have one issue with a
RS CPU spiking to 100% because of heavy inserts, but splitting a small
region manually took care of it.  We run a few MapReduce jobs that aggregate
data from one HBase table to another.  We spin those up on Amazon Elastic
MapReduce (separate nodes from our HBase cluster).


On Thu, Jul 22, 2010 at 3:56 PM, Paul Smith <psmith@aconex.com> wrote:

> anyone able to share their experience, thoughts on the 'smallest'
> production HBase cluster in operation?    Thinking there may be some point
> in the # Nodes scale where one transitions from/to "that's silly" to "that's
> actually more like it".
> Anyone out there with a small HBase cluster in operation with < 10 nodes
> able to share any information?
> I notice on http://wiki.apache.org/hadoop/Hbase/PoweredBy there are some
> who have even just a 3 node cluster, perhaps that's out of date, but curious
> to know from the community on where people think 'the line' needs to be
> drawn on usage of Hbase.
> To take things to an extreme, is there anyone actually running a _single_
> HBase node... ? (one would hope that machine is actually designed to be a
> bit more HA than normal) just to take advantage of a column-oriented store?
> thanks,
> Paul

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message