Getting no node available exception when there are many requests


(Seungjin Lee) #1

Hello all,

I'm using storm with elasticsearch percolator and normally it works as
expected.

but when there are to many requests simultaneously, some of them succeed
and some fail with no node available exception.

I think there should be a configuration about maximum requests per seconds
or something like that, and should be a way to avoid no node available
exception by queing request in the java ElasticSearch client.

Below is my code snippet for percolating

client.preparePercolate()
.setIndices("index")
.setDocumentType(projectName)
.setPercolateDoc(docBuilder().setDoc(log)).execute().actionGet();

would be glad to let me know if you have any knowledge about this, thanks.

Sincerly,

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL3_U408zgZmwLdu-SkEs%3DaZ_GFszAk1GKk6vuHbTSjutP2%3D4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(system) #2