- 최신
- 최다 투표
- 가장 많은 댓글
OK, so (not for the first time) it was my own idiocy! I thought I'd post this rather than kill the question, as it just might help someone down the line :)
I had a function called a little later that checked to see if an API Gateway integration existed for the lambda. The basic shape of the function was
get the first 50 integrations using GetIntegrationsCommand()
save the NextToken marker if there is one
iterate through the list to see if there's a match
if there is, return it
while there are more integrations
get the next 50 using GetIntegrationsCommand() <<<<<<<<
save the Next Token if there is one
iterate through the list to see if there's a match
if there is, return it
return null
The problem was I forgot to include the NextToken in the call at "<<<<<", so the call was just spinning out, getting the same results over and over, and very helpfully, generating a "Too Many Requests" exception. The results looked unpredictable, because if a match was found in the first 50, everything worked, otherwise the exception was thrown.
Now I can build and launch tens of simultaneous (hopefully hundreds!) lambdas.
Hello.
Would it improve if I increase the number of concurrent Lambda functions?
https://docs.aws.amazon.com/lambda/latest/dg/configuration-concurrency.html#configuration-concurrency-reserved
I don't think so ... I don't see why I'd need reserved instances as I'm not concerned about the startup time, and the Function concurrency configuration is "Use unreserved account concurrency" with "Unreserved account concurrency 1000" so I don't think I hit that limit.
My Builder instance(s?) seem to be stuck now, as they will build new lambdas but can't deploy them - when they try to update the function code they get the "Too many errors" exception. I don't know if this will time out at some point, but even if they do I can't have a limit of ten concurrent invocations - I need thousands :)
It's almost as if I've hit some account-wide limit?
관련 콘텐츠
- AWS 공식업데이트됨 3년 전
- AWS 공식업데이트됨 일 년 전
Another possibility is that the Lambda API execution limit was exceeded by executing UpdateFunctionCodeCommand() at the same time. According to the documentation, it is 15 requests per second. https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html#api-requests