Any idea what is causing this error Elastic 2.4.2


Some of our queries keep failing since we upgraded from 1.7.1 to 2.4.2, any idea what is causing these errors?

[2016-12-01 20:21:36,064][ERROR][marvel.agent ] [ElasticSearch-10] background thread had an uncaught exception
ElasticsearchException[failed to flush exporter bulks]
at org.elasticsearch.marvel.agent.exporter.ExportBulk$Compound.flush(
at org.elasticsearch.marvel.agent.exporter.ExportBulk.close(
at org.elasticsearch.marvel.agent.AgentService$
Suppressed: ElasticsearchException[failed to flush [default_local] exporter bulk]; nested: ElasticsearchException[failure in bulk execution:
[0]: index [.marvel-es-1-2016.12.01], type [node_stats], id [AVi8DKi8ZUbrVfwneDzJ], message [RemoteTransportException[[ElasticSearch-18][][indices:data/write/bulk[s]]]; nested: RemoteTransportException[[ElasticSearch-18][][indices:data/write/bulk[s][p]]]; nested: EsRejectedExecutionException[rejected execution of org.elasticsearch.transport.TransportService$4@5efc8094 on EsThreadPoolExecutor[bulk, queue capacity = 50, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@328300fe[Running, pool size = 8, active threads = 8, queued tasks = 60, completed tasks = 160799220]]];]];
at org.elasticsearch.marvel.agent.exporter.ExportBulk$Compound.flush(
... 3 more


Please help !!!

(Xavier Facq) #3


No guaranty, but I think it is because there is too many requests sended to the server (maybe a big bulk) and as the server is too "small" it drops some queries.


It is a 20 nodes cluster AWS r3.2xlarge, plenty of computing power

(Xavier Facq) #5

There is something wrong with threadpool and queue sizes, are your bulk very large ?

Some doc about threadpool :

(Mark Walkom) #6

That's Marvel, so what does it say about threadpool capacity?

(system) #7

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