it works. Thanks a lot.
2011/4/13 Patricio Echagüe <patric...@gmail.com> > I'll try. Thank you Tom. > > > On Wed, Apr 13, 2011 at 5:39 PM, Tom White <t...@cloudera.com> 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 <patric...@gmail.com>: >> > 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 set whirr.hardware-id = m1.large >> it >> > throws an exception saying that it is an incompatible type for the AMI. >> > >> > >> > Currently the default is m1.small and when I run the benchmark >> TestDFSIO, >> > all my datanodes are timing out. >> > >> > >> > So my thought here is that perhaps a hardware type m1.large or bigger >> can >> > help. >> > >> > >> > Any help will be much appreciated >> > >> > >> > Thanks >> > >
