I'm running ElasticSearch (0.16.2) on a dedicated cluster with 17 nodes (100
shards, currently 0 replicas). After indexing about 130 million documents,
I'm using Hadoop MapReduce to execute about 100000 queries. For my usecase I
need to fetch all hits for each query (most of them are text or span_near
queries and some yield more than 20 million IDs), so I'm using
SearchType.SCAN and scrolls in order to avoid sorting all the results.
In order to avoid overhead (and reduce the initialization time) I'm using
TransportClient instead of client-only-nodes.
Occasionally a weird error occurs, stacktrace at:
As the error doesn't occur frequently and the stack trace doesn't look like
a 'normal' network error, I think it may be a bug in ElasticSearch - I
didn't find any information on the stack trace on Google.
It would be great if anyone of you could review the stacktrace - many thanks