-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config sync hits some amazon limit #254
Comments
From amazon:
They suggested to implement retry exponential retry behavior like this |
That's a horrible code example, the JS SDK support auto retries for some of
their products. Maybe it needs to be enabled?
…On Wed, Jun 14, 2017 at 11:19 AM, Chris Olszewski ***@***.***> wrote:
From amazon:
- Describe actions, such as ListAliases, ListFunctions etc -- these
functions simply retrieve cached data, so they have the highest retry
limits.
- Modify actions, such as CreateFunction, CreateAlias, etc -- these
functions create or modify resources so they have a lower request limit
than describe actions.
They suggested to implement retry exponential retry behavior like this
<http://docs.aws.amazon.com/general/latest/gr/api-retries.html>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#254 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AABlbkAmp-seRyUKGMzClpxvnNee9dTpks5sD_nugaJpZM4N40Gw>
.
--
Francis Gulotta
Director of Engineering
Bustle.com / @bustlelabs
|
I've been playing around with |
What about no concurrency? Since this is probably account wide and not per user we might want to be conservative. |
Hi guys, is there a fix for this. Bit of a blocker for shep if maximum number of functions is limited to 10 or so?? |
I have a project with 12 functions and I get a
TooManyRequestsException: Rate exceeded
on a bunch of the Lambda API calls. Easy fix is to turn down the concurrency on thePromise.map
call.The text was updated successfully, but these errors were encountered: