Haisum Mussawir created JCLOUDS-1420:

             Summary: insert waiting time before tagging ec2 instances
                 Key: JCLOUDS-1420
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1420
             Project: jclouds
          Issue Type: Bug
          Components: jclouds-compute
    Affects Versions: 1.9.0
            Reporter: Haisum Mussawir

When EC2ComputeService.createNodesInGroup method is called it tries to apply 
tags immediately after instance creation. This results in 
InvalidInstanceID.NotFound  sometimes. This is because of eventual consistency 
in Amazon APIs as documented at 
{quote}The following are examples of error codes you may encounter as a result 
of eventual consistency.
{quote} * InvalidInstanceID.NotFound

If you successfully run the RunInstances command, and then immediately run 
another command using the instance ID that was provided in the response of 
RunInstances, it may return an InvalidInstanceID.NotFound error. This does not 
mean the instance does not exist.

A similar issue was reported and fixed in Apache Spark at 
https://github.com/apache/spark/pull/3986. It was resolved by putting some wait 
between create instance and tagging code. I think same may be needed here. I am 
using jclouds 1.9.0 and couldn't see any changes that address this issue in 
latest code. 

This message was sent by Atlassian JIRA

Reply via email to