Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Elasticsearch - No Living Connections

See original GitHub issue

This has been mentioned before here and there…but im certain this is still a bug or connections arent pooled correctly?

Im doing the following: (it indexes 6.000.000 docs…one by one…(dont wanna use bulk imports…so lets ignore this topic for a second) I’m even waiting for an index to be complete to call the next one…still at around 16.000 entries…i always get the no more living connections error.

I tried with keepalive: true/false etc. but it seems its a connection pooling issue no? iprange = array of item esearch = Elasticsearch client.

function doItem(i){
    process.stdout.write("Importing item:  " + i + "\r");
    var doc = {};
    doc.index = "geoip";
    doc.type = "location";
    doc.body = iprange[i];
    esearch.index(doc, function (err, resp) {
        if(err)
            trace.info(err);

        i++;

        if(i < len) {
            doItem(i);
        }
    });
}

doItem(1);

Issue Analytics

State:
Created 9 years ago
Reactions:26
Comments:70 (9 by maintainers)

Top GitHub Comments

36reactions

wedgemartincommented, May 30, 2017

Just wanted to add: this bug sucks. Seeing it with latest stable ( 5.4.0 ) Restarted it several times, and just running tests against it, I hit it 99.9% of the time.

19reactions

thecaddycommented, Mar 9, 2015

The error i see:

error: Error: No Living connections
    at sendReqWithConnection (.../node_modules/elasticsearch/src/lib/transport.js:174:15)
    at next (.../node_modules/elasticsearch/src/lib/connection_pool.js:213:7)
    at process._tickCallback (node.js:355:11)

Elasticsearch WARNING: 2015-03-07T00:28:39Z
  Unable to revive connection