2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hi,
Lambda service has various quotas: https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html
You should check the current values for your account via AWS Console and ask for raises when needed.
The one that comes first in mind is concurrent executions: default is at 1000 but it can be raised much higher on request
Best.
Didier
0
I would run some test from a different machine (not Lambda) the same time of the failures to check if the issue is on the GCP side or not. I would run something from your Laptop and also maybe from some EC2 instance.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
I'm very aware that AWS Lambda has concurrent execution limits, but that doesn't explain why an already executing lambda is getting TCP socket hangups against 1 major network destination specifically after 2 minutes suddenly. None of those documented limits are relevant to what I'm asking about.