# Visualize: regected execution of or.elasticsearch.common.util.concurrent.TimedRunable

**URL:** <https://discuss.elastic.co/t/visualize-regected-execution-of-or-elasticsearch-common-util-concurrent-timedrunable/154490>\
**Category:** Elasticsearch\
**Created:** [October 29, 2018, 6:45pm UTC](https://discuss.elastic.co/t/visualize-regected-execution-of-or-elasticsearch-common-util-concurrent-timedrunable/154490 "2018-10-29T18:45:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![snewman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@snewman](https://discuss.elastic.co/u/snewman)\
**Post date:** [October 29, 2018, 6:45pm UTC](https://discuss.elastic.co/t/visualize-regected-execution-of-or-elasticsearch-common-util-concurrent-timedrunable/154490/1 "2018-10-29T18:45:26Z")

</div>

I'm running a single node deployment of elasticsearch and kibana. Elasticsearch.yml is basically default with the exception of these two lines  
`xpack.security.enabled: false xpack.monitoring.collection.enabled: true`  
Elasticsearch only has about 50 gb of data. When it's loading the dashboard which is time filtered to be about 5-10 gb of data, it has been failing a lot recently. I have tried increasing the queue size, but I still get the following error:

> Visualize: rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@230cbd7b on QueueResizingEsThreadPoolExecutor[name = Tkb3qYF/search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 70ms, adjustment amount = 50, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@72046c3f[Running, pool size = 7, active threads = 7, queued tasks = 1056, completed tasks = 10452]] rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@743b1765 on QueueResizingEsThreadPoolExecutor[name = Tkb3qYF/search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 70ms, adjustment amount = 50, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@72046c3f[Running, pool size = 7, active threads = 7, queued tasks = 1057, completed tasks = 10452]] rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@5ef9168e on QueueResizingEsThreadPoolExecutor[name = Tkb3qYF/search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 70ms, adjustment amount = 50, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@72046c3f[Running, pool size = 7, active threads = 7, queued tasks = 1058, completed tasks = 10452]] rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@6788f0f1 on QueueResizingEsThreadPoolExecutor[name = Tkb3qYF/search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 70ms, adjustment amount = 50, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@72046c3f[Running, pool size = 7, active threads = 7, queued tasks = 1059, completed tasks = 10452]] rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@21a97e1e on QueueResizingEsThreadPoolExecutor[name = Tkb3qYF/search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 70ms, adjustment amount = 50, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@72046c3f[Running, pool size = 7, active threads = 7, queued tasks = 1060, completed tasks = 10452]]`

---

<div class="post-metadata">

**Author:** ![snewman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@snewman](https://discuss.elastic.co/u/snewman)\
**Post date:** [October 29, 2018, 6:49pm UTC](https://discuss.elastic.co/t/visualize-regected-execution-of-or-elasticsearch-common-util-concurrent-timedrunable/154490/2 "2018-10-29T18:49:34Z")

</div>

In addition I am getting shard failures at the same time. Here are my cluster stats:

> {  
> "\_nodes": {  
> "total": 1,  
> "successful": 1,  
> "failed": 0  
> },  
> "cluster\_name": "elasticsearch",  
> "timestamp": 1540838856206,  
> "status": "green",  
> "indices": {  
> "count": 458,  
> "shards": {  
> "total": 546,  
> "primaries": 546,  
> "replication": 0,  
> "index": {  
> "shards": {  
> "min": 1,  
> "max": 5,  
> "avg": 1.1921397379912664  
> },  
> "primaries": {  
> "min": 1,  
> "max": 5,  
> "avg": 1.1921397379912664  
> },  
> "replication": {  
> "min": 0,  
> "max": 0,  
> "avg": 0  
> }  
> }  
> },  
> "docs": {  
> "count": 184981345,  
> "deleted": 41677  
> },  
> "store": {  
> "size\_in\_bytes": 49348746297  
> },  
> "fielddata": {  
> "memory\_size\_in\_bytes": 45640,  
> "evictions": 0  
> },  
> "query\_cache": {  
> "memory\_size\_in\_bytes": 2319186,  
> "total\_count": 293892,  
> "hit\_count": 2398,  
> "miss\_count": 291494,  
> "cache\_size": 255,  
> "cache\_count": 259,  
> "evictions": 4  
> },  
> "completion": {  
> "size\_in\_bytes": 0  
> },  
> "segments": {  
> "count": 4152,  
> "memory\_in\_bytes": 152090498,  
> "terms\_memory\_in\_bytes": 104071725,  
> "stored\_fields\_memory\_in\_bytes": 28113680,  
> "term\_vectors\_memory\_in\_bytes": 0,  
> "norms\_memory\_in\_bytes": 5968128,  
> "points\_memory\_in\_bytes": 9595669,  
> "doc\_values\_memory\_in\_bytes": 4341296,  
> "index\_writer\_memory\_in\_bytes": 68310418,  
> "version\_map\_memory\_in\_bytes": 164591,  
> "fixed\_bit\_set\_memory\_in\_bytes": 377832,  
> "max\_unsafe\_auto\_id\_timestamp": 1540837861868,  
> "file\_sizes": {}  
> }  
> },  
> "nodes": {  
> "count": {  
> "total": 1,  
> "data": 1,  
> "coordinating\_only": 0,  
> "master": 1,  
> "ingest": 1  
> },  
> "versions": [  
> "6.3.0"  
> ],  
> "os": {  
> "available\_processors": 4,  
> "allocated\_processors": 4,  
> "names": [  
> {  
> "name": "Windows Server 2012 R2",  
> "count": 1  
> }  
> ],  
> "mem": {  
> "total\_in\_bytes": 17179398144,  
> "free\_in\_bytes": 3180969984,  
> "used\_in\_bytes": 13998428160,  
> "free\_percent": 19,  
> "used\_percent": 81  
> }  
> },  
> "process": {  
> "cpu": {  
> "percent": 20  
> },  
> "open\_file\_descriptors": {  
> "min": -1,  
> "max": -1,  
> "avg": 0  
> }  
> },  
> "jvm": {  
> "max\_uptime\_in\_millis": 1053510,  
> "versions": [  
> {  
> "version": "1.8.0\_162",  
> "vm\_name": "Java HotSpot(TM) 64-Bit Server VM",  
> "vm\_version": "25.162-b12",  
> "vm\_vendor": "Oracle Corporation",  
> "count": 1  
> }  
> ],  
> "mem": {  
> "heap\_used\_in\_bytes": 1960242752,  
> "heap\_max\_in\_bytes": 4260102144  
> },  
> "threads": 74  
> },  
> "fs": {  
> "total\_in\_bytes": 214745214976,  
> "free\_in\_bytes": 24940769280,  
> "available\_in\_bytes": 24940769280  
> },  
> "plugins": ,  
> "network\_types": {  
> "transport\_types": {  
> "netty4": 1  
> },  
> "http\_types": {  
> "netty4": 1  
> }  
> }  
> }  
> }

any help is appreciated

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [October 29, 2018, 7:18pm UTC](https://discuss.elastic.co/t/visualize-regected-execution-of-or-elasticsearch-common-util-concurrent-timedrunable/154490/3 "2018-10-29T19:18:06Z")

</div>

That is a lot of shards given the data volume and node size. having lots of small indices and shards can be very inefficient and lead bot performance problems, as described in [this blog post on shards and sharding practices](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster). Dramatically increasing the queues will not solve the problem, but possibly make it worse. I would recommend reducing the number of shards dramatically, which should give you less problems as well as better performance.

---

<div class="post-metadata">

**Author:** ![snewman](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@snewman](https://discuss.elastic.co/u/snewman)\
**Post date:** [October 29, 2018, 8:46pm UTC](https://discuss.elastic.co/t/visualize-regected-execution-of-or-elasticsearch-common-util-concurrent-timedrunable/154490/4 "2018-10-29T20:46:56Z")

</div>

Thank you. I will give that a try

---

<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:** [November 26, 2018, 8:46pm UTC](https://discuss.elastic.co/t/visualize-regected-execution-of-or-elasticsearch-common-util-concurrent-timedrunable/154490/5 "2018-11-26T20:46:59Z")

</div>

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