Setting whirr.hardware-id=m1.small produced the same large data dump. Setting whirr.hardware-id=c1.xlarge produced this error:
org.jclouds.http.HttpResponseException: command: POST https://ec2.us-east-1.amazonaws.com/ HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content: [Non-Windows AMIs with a virtualization type of 'hvm' currently may only be used with Cluster Compute instance types.] I'm sorry if I'm being dense here. Getting a basic hadoop cluster to work using whirr.hardware-id=c1.medium whirr.image-id=us-east-1/ami-d59d6bbc was so easy that I was excited to try hbase. I'm just not understanding the error messages enough to guess how to result these issues. On Thu, Dec 22, 2011 at 2:10 PM, Andrei Savu <[email protected]> wrote: > On Thu, Dec 22, 2011 at 9:08 PM, David Medinets <[email protected]> >> Do I need use to use a larger instance type? > > Yes, t1.micro is not really suitable to run something like Hadoop & HBase. > It should work with m1.small just fine.
