# Any idea what is causing this error Elastic 2.4.2

**URL:** <https://discuss.elastic.co/t/any-idea-what-is-causing-this-error-elastic-2-4-2/67806>\
**Category:** Elasticsearch\
**Created:** [December 1, 2016, 8:37pm UTC](https://discuss.elastic.co/t/any-idea-what-is-causing-this-error-elastic-2-4-2/67806 "2016-12-01T20:37:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![genesis](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@genesis](https://discuss.elastic.co/u/genesis)\
**Post date:** [December 1, 2016, 8:37pm UTC](https://discuss.elastic.co/t/any-idea-what-is-causing-this-error-elastic-2-4-2/67806/1 "2016-12-01T20:37:51Z")

</div>

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(ExportBulk.java:104)  
at org.elasticsearch.marvel.agent.exporter.ExportBulk.close(ExportBulk.java:53)  
at org.elasticsearch.marvel.agent.AgentService$ExportingWorker.run(AgentService.java:201)  
at java.lang.Thread.run(Thread.java:745)  
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][10.10.0.112:9300][indices:data/write/bulk[s]]]; nested: RemoteTransportException[[ElasticSearch-18][10.10.0.112:9300][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(ExportBulk.java:106)  
... 3 more

---

<div class="post-metadata">

**Author:** ![genesis](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@genesis](https://discuss.elastic.co/u/genesis)\
**Post date:** [December 2, 2016, 3:12pm UTC](https://discuss.elastic.co/t/any-idea-what-is-causing-this-error-elastic-2-4-2/67806/2 "2016-12-02T15:12:50Z")

</div>

Please help !!!

---

<div class="post-metadata">

**Author:** ![xavierfacq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavierfacq/32/8744_2.png) [@xavierfacq](https://discuss.elastic.co/u/xavierfacq)\
**Post date:** [December 2, 2016, 8:22pm UTC](https://discuss.elastic.co/t/any-idea-what-is-causing-this-error-elastic-2-4-2/67806/3 "2016-12-02T20:22:08Z")

</div>

hi,

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.

---

<div class="post-metadata">

**Author:** ![genesis](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@genesis](https://discuss.elastic.co/u/genesis)\
**Post date:** [December 2, 2016, 8:25pm UTC](https://discuss.elastic.co/t/any-idea-what-is-causing-this-error-elastic-2-4-2/67806/4 "2016-12-02T20:25:28Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![xavierfacq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavierfacq/32/8744_2.png) [@xavierfacq](https://discuss.elastic.co/u/xavierfacq)\
**Post date:** [December 2, 2016, 8:43pm UTC](https://discuss.elastic.co/t/any-idea-what-is-causing-this-error-elastic-2-4-2/67806/5 "2016-12-02T20:43:37Z")

</div>

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

Some doc about threadpool : [https://www.elastic.co/guide/en/elasticsearch/reference/5.0/modules-threadpool.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/modules-threadpool.html)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 2, 2016, 8:44pm UTC](https://discuss.elastic.co/t/any-idea-what-is-causing-this-error-elastic-2-4-2/67806/6 "2016-12-02T20:44:33Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 30, 2016, 8:44pm UTC](https://discuss.elastic.co/t/any-idea-what-is-causing-this-error-elastic-2-4-2/67806/7 "2016-12-30T20:44:43Z")

</div>

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