As long as we are all clear about the usefulness of a single host system. For map-reduce over BigTable, nothing more than development, functional testing, and toy demo scenarios.
- Andy ----- Original Message ---- > From: Otis Gospodnetic <[email protected]> > To: [email protected] > Sent: Fri, January 15, 2010 2:30:34 PM > Subject: Re: HBase on 1 box? how big? > > Heh, I like the analogies! :) > Yes, it makes no sense to use HBase for production data volumes, etc., but > this > might be handy for development. > Or for a demo that needs to consists of the same pieces (daemons, configs, > etc.) > on 1 box, so that one can easily move it to a proper, big cluster, without > re-engineering or replacing any of the components. > > For example, you may have an app that you want to demo to a customer, and you > can't ask them for N boxes for the demo. But you can ask them for 1 box to > install something on. > > Or maybe you can run everything from a memory stick? ;) Hey, is there a > technical reason why having all jars, scripts, configs, etc. on a stick, and > have the configs point to dirs on the stick for holding data? I'm not > joking, > really! :) > > Thanks, > Otis > > > ----- Original Message ---- > > From: Andrew Purtell > > To: [email protected] > > Sent: Fri, January 15, 2010 4:17:35 PM > > Subject: Re: HBase on 1 box? how big? > > > > 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: [email protected] > > > 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
