On Feb 3, 2014, at 6:28 PM, Andrew Bayer <andrew.ba...@gmail.com> wrote:
> So I'm trying to figure out how to make it possible to provision 100+ > instances on EC2 in one createNodesInGroup call without getting crushed by > API rate limits. The combination of the min count/max count parameters and > the idempotency with a client token (see > http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Run_Instance_Idempotency.html) > makes the raw creation of 100+ instances without a thundering herd of > RunInstances calls very realistic, but then we hit the issue of polling > those nodes (even with the idempotency, we'd still end up having at least > one is-node-running polling call per node, and then we'd hit the same thing > but much bigger at terminate/pause/resume/etc)… The way I’ve dealt with this in the past is by using POLL_INITIAL_PERIOD and POLL_MAX_PERIOD [1]. Does that work for your use case? Everett [1] https://github.com/jclouds/jclouds-examples/blob/master/rackspace/src/main/java/org/jclouds/examples/rackspace/cloudservers/CloudServersPublish.java#L102-103