Re: image-id to specify a m1.large hardware in EC2
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 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
Re: image-id to specify a m1.large hardware in EC2
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 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 >
Re: image-id to specify a m1.large hardware in EC2
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 >> >> 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 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 >> > >
Re: image-id to specify a m1.large hardware in EC2
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 past this point. Any
suggestions/thoughts? My properties file is also attached [2].
Alternatively, can anyone recommend an existing EBS-backed AMI that
works with whirr Java? I understand the configurable EBS volumes are
still being worked on; here, I was just hoping to get an EBS-backed
root volume.
Norbert
[1]
tts-unixudp05516758uds:ec2 nburger$ whirr launch-cluster --config
cvps.properties
Bootstrapping cluster
Configuring template
Starting 1 node(s) with roles [hadoop-datanode, hadoop-tasktracker,
hbase-regionserver]
Configuring template
Starting 1 node(s) with roles [zookeeper, hadoop-namenode,
hadoop-jobtracker, hbase-master]
<< problem applying options to node(us-east-1/i-a84f35c7):
org.jclouds.ssh.SshException: ec2-user@184.73.147.242:22: Error
connecting to session.
at org.jclouds.ssh.jsch.JschSshClient.propagate(JschSshClient.java:252)
at org.jclouds.ssh.jsch.JschSshClient.connect(JschSshClient.java:206)
at
org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.call(RunScriptOnNodeAsInitScriptUsingSsh.java:90)
at
org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:140)
at
org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:56)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Caused by: com.jcraft.jsch.JSchException: Auth fail
at com.jcraft.jsch.Session.connect(Session.java:461)
at com.jcraft.jsch.Session.connect(Session.java:154)
at org.jclouds.ssh.jsch.JschSshClient.newSession(JschSshClient.java:247)
at org.jclouds.ssh.jsch.JschSshClient.connect(JschSshClient.java:186)
... 8 more
[2]
whirr.cluster-name=cvps
whirr.instance-templates=1
zookeeper+hadoop-namenode+hadoop-jobtracker+hbase-master,1
hadoop-datanode+hadoop-tasktracker+hbase-regionserver
whirr.hadoop-install-function=install_cdh_hadoop
whirr.hadoop-configure-function=configure_cdh_hadoop
whirr.provider=aws-ec2
whirr.identity=${env:AWS_ACCESS_KEY_ID}
whirr.credential=${env:AWS_SECRET_ACCESS_KEY}
whirr.hardware-id=m1.large
whirr.image-id=us-east-1/ami-1ce71b75
jclouds.ec2.ami-owners=130611044146
whirr.location-id=us-east-1
whirr.login-user=ec2-user
whirr.private-key-file=cvps-ssh
whirr.public-key-file=cvps-ssh.pub
