This archive was generated by
I put in a new tagging system for the nodes' aliases that's much faster
but unfortunately reintroduced this bug yet again. It should be fixed
now in the latest github code. Please reinstall the latest github code
and let me know if you have any issues.
On 04/04/2011 03:40 PM, Austin Godber wrote:
> Thats one of those eventual consistency errors that one needs to retry
> on, the code should retry that is. I saw this all the time in some
> other code of mine ... it goes like this:
> Launch AMI
> store returned instance ID
> try to do something with instance id
> instance ID doesn't exist?!?
> I don't really have a SC specific answer though, sorry.
> On 04/04/2011 03:24 PM, Gaston Fiore wrote:
>> Hi Justin,
>> I'm not sure what the issue below is...
>> cloudera_at_cloudera-demo:~/hw4$ starcluster start mr5
>> StarCluster - (http://web.mit.edu/starcluster) (v. 0.9999)
>> Software Tools for Academics and Researchers (STAR)
>> Please submit bug reports to starcluster_at_mit.edu
>>>>> Using default cluster template: smallcluster
>>>>> Validating cluster template settings...
>>>>> Cluster template settings are valid
>>>>> Starting cluster...
>>>>> Launching a 5-node cluster...
>>>>> Creating security group _at_sc-mr5...
>> cli.py:162 - ERROR - InvalidInstanceID.NotFound: The instance ID
>> 'i-1660e779' does not exist
>> StarCluster mailing list
> StarCluster mailing list
Received on Mon Apr 04 2011 - 18:19:15 EDT