New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EEXIST error when using functions_worker_process_count #1230
Comments
This was referenced Jan 29, 2024
JacksonWeber
added a commit
to Azure/azure-sdk-for-js
that referenced
this issue
Feb 2, 2024
…for Telemetry Caching (#28399) ### Packages impacted by this PR @azure/monitor-opentelemetry-exporter ### Issues associated with this PR microsoft/ApplicationInsights-node.js#1230 ### Describe the problem that is addressed by this PR Append the process ID to the file name created for holding disk cached telemetry. This should resolve the issue with multiple Azure Functions cores attempting to read/write/delete the same file when functions are scaled to use multiple cores. Extended this logic outside of Azure Functions so that in any case where the SDK could be run concurrently we create distinct cache files. ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ### Checklists - [x] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [x] Added a changelog (if necessary)
v-weiyding
pushed a commit
to v-weiyding/azure-sdk-for-js
that referenced
this issue
Feb 4, 2024
…for Telemetry Caching (Azure#28399) ### Packages impacted by this PR @azure/monitor-opentelemetry-exporter ### Issues associated with this PR microsoft/ApplicationInsights-node.js#1230 ### Describe the problem that is addressed by this PR Append the process ID to the file name created for holding disk cached telemetry. This should resolve the issue with multiple Azure Functions cores attempting to read/write/delete the same file when functions are scaled to use multiple cores. Extended this logic outside of Azure Functions so that in any case where the SDK could be run concurrently we create distinct cache files. ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ### Checklists - [x] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [x] Added a changelog (if necessary)
@ejizba Just wanted to confirm with you that the solution implemented in the above PRs works for you. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Azure Functions, users can have multiple processes on the same instance if they use the
functions_worker_process_count
setting (docs here). Unfortunately that can lead to the following uncaught exception:I don't know the best behavior here, but at minimum this error should be handled more gracefully instead of throwing an uncaught exception which can crash the Node.js process.
The text was updated successfully, but these errors were encountered: