StarCluster - Mailing List Archive

invalid instance error

From: Igor Tatarinov <no email>
Date: Sun, 19 Dec 2010 14:23:31 -0800

I've seen a few of these intermittent errors right at start up:

PID: 29470 cli.py:158 - ERROR - InvalidInstanceID.NotFound: The instance ID
'i-2eaea843' does not exist

I think EC2 needs a few seconds after starting a new instance before it can
be queried about the new instance. Adding an initial delay seems to fix this
problem:

_at__at_ -1168,6 +1168,7 @@
         s = Spinner()
         log.log(INFO_NO_NEWLINE, "Waiting for cluster to come up...")
         s.start()
+ time.sleep(30)
         while not self.is_cluster_up(enforce_size):
             time.sleep(30)
         s.stop()

30 seconds is probably overkill but I doubt a new instance can be spun up in
less than that.

igor
Received on Sun Dec 19 2010 - 17:23:56 EST
This archive was generated by hypermail 2.3.0.

Search:

Sort all by:

Date

Month

Thread

Author

Subject