Open enricoschaaf opened 9 months ago
We have seen the same issue. Using Datadog layers as you seem to be using. We are trying to debug, I'll update this ticket if we get any more insight.
Datadog has released new version of lambda instrumentation, which fixed the issue for us.
Thanks for reporting this, I was meaning to report this too.
The EMFILE
error appears to be due to npm install
using more than 1,024 file descriptors, which is the AWS Lambda hard limit (source: https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html).
Two paths I found, that are unrealistic:
npm install
to reduce the number of open files it usesHope this can get someone kickstarted on the issue, as would be great to use Codebuild with Lambda execution engine to do the build
Describe the bug When switching from node 18 to node 20 we noticed a lot of EMFILE and EBUSY that we never had before.
To Reproduce This is really hard to reproduce it only happens sometimes when making network requests.
Expected behavior No error to appear
Logs
Platform (please complete the following information): node20 x86_64
Additional context Not sure if this an issue with the image or the lambda runtime so please let me know if another repo makes more sense