Hi all -- I'm trying to launch an HBase cluster with a custom AMI
(EBS-backed root volume) and I'm running into the same stack trace
I've seen earlier on this list (an SSH exception when trying to
contact the master [1]). Looking through the archives, it doesn't
seem like anyone had luck getting p
it works. Thanks a lot.
2011/4/13 Patricio Echagüe
> I'll try. Thank you Tom.
>
>
> On Wed, Apr 13, 2011 at 5:39 PM, Tom White wrote:
>
>> Hi Patricio,
>>
>> In the past I've used
>>
>> whirr.hardware-id=m1.large
>> whirr.image-id=us-east-1/ami-da0cf8b3
>> whirr.location-id=us-east-1
>>
>> Hop
I'll try. Thank you Tom.
On Wed, Apr 13, 2011 at 5:39 PM, Tom White wrote:
> Hi Patricio,
>
> In the past I've used
>
> whirr.hardware-id=m1.large
> whirr.image-id=us-east-1/ami-da0cf8b3
> whirr.location-id=us-east-1
>
> Hope that helps.
>
> Tom
>
> 2011/4/13 Patricio Echagüe :
> > Hi all, I nee
Hi Patricio,
In the past I've used
whirr.hardware-id=m1.large
whirr.image-id=us-east-1/ami-da0cf8b3
whirr.location-id=us-east-1
Hope that helps.
Tom
2011/4/13 Patricio Echagüe :
> Hi all, I need to create m1.large EC2 nodes in EC2 and was wondering if
> someone knows what image-id to specify i
Hi all, I need to create *m1.large* EC2 nodes in EC2 and was wondering if
someone knows what image-id to specify in the properties file for whirr in
order to do that.
whirr.image-id=*ami-2a1fec43 (apparently the default doesn't work for
m1.large hardware)*
with the previously default ami, if I
