StarCluster - Mailing List Archive

Re: [Starcluster] InvalidInstanceID.NotFound on Disk Creation

From: Justin Riley <no email>
Date: Sun, 22 Aug 2010 22:06:51 -0400

Hi Austin,

Yes the VolumeCreator class shuts down all instances in the _at_sc-volumecreator security group after successful creation of a volume by default. If you run two volume creator sessions at the same time they will attempt to use the same host. Whichever finishes first will shutdown the instance (unless you tell it not to) which breaks things for the other session. If you want to run two volume creator sessions at the same time you should pass the --no-shutdown option to the createvolume command or use shutdown_instance=False in the VolumeCreator class's constructor if you're using the class directly. After the volumes have been created successfully you can run the following command to shut down the volume host instance(s):

$ starcluster stop volumecreator

Hope that helps,

From: starcluster-bounces_at_MIT.EDU [starcluster-bounces_at_MIT.EDU] On Behalf Of Austin Godber []
Sent: Sunday, August 22, 2010 7:55 PM
Subject: [Starcluster] InvalidInstanceID.NotFound on Disk Creation

Has anyone else seen an InvalidInstanceID error when creating a disk?

I got the following error when creating a disk: - ERROR - exception thrown: EC2ResponseError: 400 Bad Request
<?xml version="1.0"?>
instance ID 'i-913c54fb' does not

The instance definitely started since I see it as terminated in my AWS
console. Oh, I bet I know what happened. I was actually creating TWO
disks at the same time. I bet that disk creation shuts down all
instances in the _at_sc-volumecreator group. And when the first one was
killed, the second one was killed along with it.

Starcluster mailing list
Received on Sun Aug 22 2010 - 22:06:52 EDT
This archive was generated by hypermail 2.3.0.


Sort all by: