- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello,
The error relates to the underlying Lambda function, so you have either reached the default account limit of 1000 parallel lambda executions. Or the lambda you're trying to execute has a configured concurrency that you max out.
https://docs.aws.amazon.com/lambda/latest/dg/configuration-concurrency.html
The MaxConcurrency on the StepFunction relates to the specific Step in that execution. So if you have a Type: Map
with MaxConcurrency: 200
, then do 6 executions on that StepFunction, and you will execute 1200 lambdas in parallel.
The Lambda limits is shared by the whole account and region, so any other execution on any lambda might contribute the problem as well.
I storing recommend that you FunctionConcurrency on lambdas that will be triggered this much so that they don't affect the rest of your account executions.
Hope this helps!
Regards,
Carl Östrand
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
i am facing below error while Edit concurrency in function configuration
The unreserved account concurrency can't go below 10.
I am facing this issue with 120 request (from csv file reading) then calling calling step function by using above yml configuration. Error": "Lambda.TooManyRequestsException"
Please keep in mind that these limits are on the Account level so if: Lambda_1 have 500 reserved concurrency (out of 1000). Lambda_2 have 400 reserved concurrency.
Now you can maximum give Lambda_3 90 reserved concurrency, otherwise, you will get the error: "The unreserved account concurrency can't go below 10."
So if you now give Lambda_3 90 reserved concurrency, you only have 10 executions left. So Lambda_4 is at a high risk of getting Lambda.TooManyRequestsException error, especially if you run 120 parallel executions.
To resolve this issue, I would:
Hope it helps!