brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-394) "Request limit exceeded" on Amazon
Date Wed, 23 Nov 2016 12:01:07 GMT


ASF GitHub Bot commented on BROOKLYN-394:

Github user asfgit closed the pull request at:

> "Request limit exceeded" on Amazon
> ----------------------------------
>                 Key: BROOKLYN-394
>                 URL:
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Svetoslav Neykov
> Any moderately sized blueprint could trigger {{Request limit exceeded}} on Amazon (say
kubernetes). The only way users have control over the request rate is by setting {{maxConcurrentMachineCreations}}
with the current recommended value of 3 (see
> It's bad user experience if one needs to adapt the location based on the blueprint.
> Possible steps to improve:
> * Add to troubleshooting documentation
> * Make maxConcurrentMachineCreations default to 3
> * Check are we polling for machine creation too often.
> * Check how many requests are we hitting Amazon with (per created machine)
> * The number of requests per machine could vary from blueprint to blueprint (say if the
blueprint is creating security networks, using other amazon services). Is there a way to throttle
our requests to amazon and stay below a certain limit per second?
> * I've hit the error during machine tear down as well, so {{maxConcurrentMachineCreations}}
is not enough to work around
> Some docs on rate limits at
> Related:

This message was sent by Atlassian JIRA

View raw message