2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi,
A common cause of EBUSY getaddrinfo is running out of file descriptors. This may come from underlying the kernel shared by all the Lambda containers.
So, yes, not much that you can do!
Unless your Lambda opens lots of files or tcp sockets in parallel.... which is probably not the case. You may reach such a case with tcp sockets if your Lambda has high throughput with lots of parallel executions of it on same server: reducing tcp sessions to a very minimum may solve your issue because it will free descriptors.
Best,
Didier
0
I don't have a specific answer, but I hope this will be helpful.
https://repost.aws/knowledge-center/lambda-intermittent-consistent-dns-error
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a 7 mois
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 3 ans
So what are our options? Ditch AWS Lambda? This causes severe downgrade in our production environment.