Hi Whirr hackers!

I am a student involved in Google Summer of Code 2013. My project topic is to test using Apache Whirr to deploy a hadoop cluster on CloudStack. Could I get some pointers on the following exception?

Running on provider cloudstack using identity rAjC7-QnUSTFytYJ7n-vi2Ku-vc5rZuAG3JeYz34fHw7zEzndFjjNmNwVZyfVZH3XqkJR8M09LKv8Pzmrr5emA Exception in thread "main" java.lang.RuntimeException: java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: Too many instance failed while bootstrapping! 0 successfully started instances while 2 instances failed at org.apache.whirr.ClusterController.launchCluster(ClusterController.java:128) at org.apache.whirr.cli.command.LaunchClusterCommand.run(LaunchClusterCommand.java:69) at org.apache.whirr.cli.command.LaunchClusterCommand.run(LaunchClusterCommand.java:59)
        at org.apache.whirr.cli.Main.run(Main.java:69)
        at org.apache.whirr.cli.Main.main(Main.java:102)
Caused by: java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: Too many instance failed while bootstrapping! 0 successfully started instances while 2 instances failed at org.apache.whirr.actions.BootstrapClusterAction.doAction(BootstrapClusterAction.java:125) at org.apache.whirr.actions.ScriptBasedClusterAction.execute(ScriptBasedClusterAction.java:131) at org.apache.whirr.ClusterController.bootstrapCluster(ClusterController.java:137) at org.apache.whirr.ClusterController.launchCluster(ClusterController.java:113)
        ... 4 more
Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Too many instance failed while bootstrapping! 0 successfully started instances while 2 instances failed
        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
        at java.util.concurrent.FutureTask.get(FutureTask.java:111)
at org.apache.whirr.actions.BootstrapClusterAction.doAction(BootstrapClusterAction.java:120)
        ... 7 more
Caused by: java.io.IOException: Too many instance failed while bootstrapping! 0 successfully started instances while 2 instances failed at org.apache.whirr.compute.StartupProcess.call(StartupProcess.java:93) at org.apache.whirr.compute.StartupProcess.call(StartupProcess.java:41)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:722)

CloudStack is running ok, with templates properly registered. I can start a VM using the Cloudstack UI. The configuration file I passed to whirr is as follows:

whirr.cluster-name=test-base-cluster
whirr.store-cluster-in-etc-hosts=true
whirr.instance-templates=1 noop
whirr.image-id=6044705e-e432-11e2-995f-0023ae94f722
whirr.hardware-id=c9c6de44-5265-4eef-b372-39f1f2cc8803
whirr.provider=cloudstack
whirr.cluster-user=$(sys:user.name)
whirr.store-cluster-in-etc-hosts=true
whirr.private-key-file=${sys:user.home}/.ssh/id_rsa
whirr.public-key-file=${sys:user.home}/.ssh/id_rsa.pub


At this moment, I want to start a basic cluster without any roles. The image-id here is the default template (centOS 5.5) shipped with CloudStack. I am using the default small instance(specified in whirr.hardware-id). In Whirr Configuration guide it is said that The type of hardware to use for the instance must be compatible with the image ID. Could someone please explain what is "compatible" in this context?

Also I watched the VM state in CloudStack UI. There are two virtual machines started although I only ask for one node in the properties file.(If I asked for two nodes, four will be started but all failed in the end.) The virtual machines went through the following states quickly: starting, running, stopping,destroyed. Why do the virtual machines die quickly?



The management-server.log in /var/log/cloudstack/management/management-server.log doesn't provide much information about the above exception. Are there any other logs that might be helpful?

Thanks for your help.

Cheers,
Meng

Reply via email to