Get EADDRNOTAVAIL after creating ~16.000 docs about elasticsearch-js HOT 12 CLOSED

I believe it is because of the keepAlive: false in your config. This is going to cause new connections to be created for each request, I suggest using keepAlive.

from elasticsearch-js.

Nope, I initially tried it with standard configuration. No difference with any keepAlive setting.

client = new elasticsearch.Client({
    host: 'localhost:9200',
});

from elasticsearch-js.

Using the bulk works pretty well.

from elasticsearch-js.

Yes, that's certainly a good idea if you have access to multiple requests at a time.

I'm almost certain that EADDRNOTAVAIL is directly related to opening and closing tcp sockets, but if you are not modifying the keepAlive/maxSockets/minSockets config then it should be opening 10 sockets and keeping them alive, no more, no less. As I walk through the forever-agent module I'm not sure that is the case. Do you have a script you can share that reproduces this?

from elasticsearch-js.

This small code does the job

var elasticsearch = require('elasticsearch'),
    async = require('async'),
    _ = require('underscore'),
    client;

client = new elasticsearch.Client({
    host: 'localhost:9200'
});

async.eachSeries(_.range(20000), function (value, done) {
    client.create({index: 'tests', type: 'test', body: {something: true, value: value}}, done);
});

from elasticsearch-js.

alright, I found the problem and submitted request/forever-agent#16. Working on a solution for the meantime.

from elasticsearch-js.

Version 1.5.10 includes a fix that should force forever-agent to use the connection pool for all requests. If you have time to confirm I would appreciate it.

from elasticsearch-js.

I'm using 1.5.11 and I'm still getting this error. Did it get reintroduced?

from elasticsearch-js.

Well, this is embarrassing. It looks like I didn't test the solution I committed and it didn't actually do what I thought it did, sorry about that.

Using @Nomeasmo's script I was able to reproduce the issue and create a verified fix. Creating a test case for this that can run automatically is pretty tricky, but it is on my todo list.

@smithatlanta or @Nomeasmo if either of you have time to verify that things are working for you too, I would really appreciate it.

https://gist.github.com/spenceralger/9550110

from elasticsearch-js.

That solved my issue. Loaded 1/4 of a million items with no issues. Thanks.

from elasticsearch-js.

Glad to hear.

from elasticsearch-js.

@spalger I am facing the exact same issue running OSX 10.10.2 , node v0.12.7, and ES 1.6.0

I am able to replicate the issue using the sample code from @Nomeasmo above. Could this issue needs to be resolved differently in 0.12 given the different http pooling?

from elasticsearch-js.