Using the @elastic/elasticsearch npm library, I see the following error when running a percolate query:
Unhandled rejection NoLivingConnectionsError: There are no living connections at makeRequest (.../node_modules/@elastic/elasticsearch/lib/Transport.js:112:25) at onResponse (.../node_modules/@elastic/elasticsearch/lib/Transport.js:208:21) at ClientRequest.request.on (.../node_modules/@elastic/elasticsearch/lib/Connection.js:89:9) at ClientRequest.emit (events.js:198:13) at Socket.emitRequestTimeout (_http_client.js:662:40) at Object.onceWrapper (events.js:286:20) at Socket.emit (events.js:198:13) at Socket._onTimeout (net.js:442:8) at ontimeout (timers.js:436:11) at tryOnTimeout (timers.js:300:5) at listOnTimeout (timers.js:263:5) at Timer.processTimers (timers.js:223:10)
However, I only see this when I have a large number of percolate documents. Right now, I have just over 350,000. But in documentation on performance of percolate queries this does not seem completely unreasonable. Execution time on this page references queries numbers from 100k - 1m.
For additional reference, this error is almost certainly related to the number of documents: when I have only a few thousand things the same ES request runs normally.
Is this a known issue? I couldn't find it. Does anyone know what is going on here?