# When trying to percolate: Unhandled rejection NoLivingConnectionsError: There are no living connections

**URL:** <https://discuss.elastic.co/t/when-trying-to-percolate-unhandled-rejection-nolivingconnectionserror-there-are-no-living-connections/227218>\
**Category:** Elasticsearch\
**Created:** [April 9, 2020, 12:02am UTC](https://discuss.elastic.co/t/when-trying-to-percolate-unhandled-rejection-nolivingconnectionserror-there-are-no-living-connections/227218 "2020-04-09T00:02:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmwilkinson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jmwilkinson/32/65961_2.png) [@jmwilkinson](https://discuss.elastic.co/u/jmwilkinson)\
**Post date:** [April 9, 2020, 12:02am UTC](https://discuss.elastic.co/t/when-trying-to-percolate-unhandled-rejection-nolivingconnectionserror-there-are-no-living-connections/227218/1 "2020-04-09T00:02:17Z")

</div>

Using the @elastic/elasticsearch npm library, I see the following error when running a percolate query:

```auto
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.

> **[When and How to Scale Percolator](https://www.elastic.co/blog/when-and-how-to-percolate-1)**
>
> Discussion when Percolator is appropriate vs Watcher in ElasticSearch. Covers scaling considerations of Percolator and tools for optimizing.

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?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 7, 2020, 12:02am UTC](https://discuss.elastic.co/t/when-trying-to-percolate-unhandled-rejection-nolivingconnectionserror-there-are-no-living-connections/227218/2 "2020-05-07T00:02:19Z")

</div>

Closed on May 7, 2020, 12:02am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.