Sounds like a yummy patch, Ryan, if you need another nudge. :) Otis
----- Original Message ---- > From: Ryan Rawson <ryano...@gmail.com> > To: hbase-user@hadoop.apache.org > Sent: Fri, January 15, 2010 5:00:42 PM > Subject: Re: HBase on 1 box? how big? > > Yes I do plan on releasing a patch, but i need to rebase it to trunk. > It moves a class from test -> java (ie; the ZK in JVM startup class). > > maybe soon? > -ryan > > On Fri, Jan 15, 2010 at 1:57 PM, Andrew Purtell wrote: > > That would be good for developing disconnected against the API. Any > > plan on releasing a patch Ryan? > > > > - Andy > > > > > > > > ----- Original Message ---- > >> From: Ryan Rawson > >> To: hbase-user@hadoop.apache.org > >> Sent: Fri, January 15, 2010 1:50:32 PM > >> Subject: Re: HBase on 1 box? how big? > >> > >> You can run HBase on any size of machine all single node, by default > >> when you start hbase it will store files in /tmp and everything is in > >> 1 JVM. How much data can you jam in there? I'm not totally sure, > >> probably a lot more than you might think, but again limited by the > >> disk. I run it on my mac laptop for example. > >> > >> I have a patch that will allow a single JVM including zookeeper, but > >> it is locked up in my private git for now. This would get rid of the > >> need to ssh localhost just to start local hbase. > >> > >> -ryan > >> > >> On Fri, Jan 15, 2010 at 1:22 PM, Seth Ladd wrote: > >> > I agree. HBase in a box is essentially MySQL. HBase is built for a > cluster. > >> > > >> > On Fri, Jan 15, 2010 at 11:17 AM, Andrew Purtell wrote: > >> >> On that scale, why not use MySQL or Postgres? > >> >> > >> >> "HBase in a box" is like "dynamic equilibrium", or "virtual reality", or > >> >> "jumbo shrimp"... :-) > >> >> > >> >> - Andy > >> >> > >> >> > >> >> > >> >> ----- Original Message ---- > >> >>> From: Otis Gospodnetic > >> >>> To: hbase-user@hadoop.apache.org > >> >>> Sent: Fri, January 15, 2010 12:54:42 PM > >> >>> Subject: HBase on 1 box? how big? > >> >>> > >> >>> Hello, > >> >>> > >> >>> I understand running HBase on a single box is kind of > >> >>> pointless (thanks Andrew Purtell for the reply about numbers of > >> >>> boxes)... but I was wondering what kind of box might one need to > >> >>> host/run various HBase/Hadoop processes? > >> >>> > >> >>> Imagine I just need to have "HBase in a box", so to speak. :) > >> >>> > >> >>> I understand it depends on the volume on data, DB structure, request > >> rates... > >> >>> I don't have those numbers, but say I want HBase to have 100M rows with > >> >>> data from Apache logs and want to run the common web analytics/stats > >> >>> reports on a nightly basis. > >> >>> > >> >>> * Would an EC2 Large Instance suffice? > >> >>> -- Large Instance 7.5 GB of memory, 4 EC2 Compute Units (2 virtual > >> >>> cores > >> >>> with 2 EC2 Compute Units each), 850 GB of local instance storage, > >> >>> 64-bit > >> >>> platform > >> >>> > >> >>> * How about EC2 Small Instance? > >> >>> -- Small Instance (Default) 1.7 GB of memory, 1 EC2 Compute Unit (1 > virtual > >> core > >> >>> with 1 EC2 Compute Unit), 160 GB of local instance storage, 32-bit > platform > >> >>> > >> >>> Thanks, > >> >>> Otis > >> >>> P.S. > >> >>> hw specs from http://aws.amazon.com/ec2/#instance > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> > > > > > > > > > > > > >
