AWS Request Rate
john at arbash-meinel.com
Fri Feb 21 03:54:58 UTC 2014
We also ended up with an instance updater that makes a request on a pretty
fast poll when you bring new instances up. It should be changed to poll for
all unknown instances in a single bulk request. Possibly the poll instance
should also be decreased. (I triggered it with just deploy -n 15, and as
early as the third instance would fail)
Also, Limit Exceeded should be treated as a temporary failure. I'm ok if we
have other failures to provision be fatal, but that one is pretty obvious.
On Feb 21, 2014 1:10 AM, "David Cheney" <david.cheney at canonical.com> wrote:
> It could be related, I know that John, Andrew and Dimiter landed some
> fixes a while back that made juju more frugal with it's AWS query usage.
> On Fri, Feb 21, 2014 at 7:32 AM, David Britton <
> david.britton at canonical.com> wrote:
>> On Fri, Feb 21, 2014 at 06:59:53AM +1100, David Cheney wrote:
>> > Which version of Juju. I could get juju into state pretty easily a few
>> > months ago
>> Interestingly enough, I just upgraded to trusty (1.17 juju line) and
>> noticed the
>> significant speed improvements in contacting AWS. I'm wondering if that
>> is responsible for me hitting this request rate limit.
>> David Britton <david.britton at canonical.com>
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Juju