Comments (1)
spalger
commented on May 19, 2024
It looks like connect ENOENT errors come from sockets when they encounter a DNS lookup error. My hunch is that there was some underlying networking error which may have gone away, or that using disposable sockets is hiding.
Can you verify that re-enabling the agent causes the error to return? While doing that could you also set the logging level to trace and share the output along with your config?
I looked through the ForeverAgent code and confirmed that all it does is handle socket availability. Node's HttpAgent takes care of all the network logic, which is still the case when you remove ForeverAgent from the mix. With that, I'm inclined to think ForeverAgent is not to blame.
from elasticsearch-js.
Related Issues (20)
- Content-Type header being changed to "text/plain" from "application/json" somewhere in the process of publishing a document to self-hosted Elasticsearch HOT 5
- Global client context not passed to Transport in 7.13.0 HOT 1
- Support for ES|QL HOT 2
- enum and/or type guard for QueryDslTextQueryType HOT 1
- search_after with sort on nested fields HOT 1
- Redaction mechanism transform arrays properties into objects HOT 1
- Nuxt 3 compatibility HOT 1
- Using the `[]` chars for an enrich policy name isn't wrapped correctly on `deletePolicy` method HOT 1
- ProductNotSupportedError: The client noticed that the server is not a supported distribution of Elasticsearch HOT 1
- Add types for plugins HOT 2
- Error parsing undici module in Next.js 14 project HOT 3
- MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 product-check listeners added HOT 2
- test issue
- Always return statusCode property.
- Stack traces are not informative when using `HttpConnection`
- Can't use asStream with body on v8 but docs say we can HOT 2
- Inserting geo_point value modifies index mapping HOT 1
- [ESQL] Version is a required field HOT 3
- Incorrect TypeScript typings for `function_score` HOT 1
- as the concurrency number increasingly, the code is still passing successfully after `requestTimeOut`ms
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from elasticsearch-js.