# Queue Capacity Sizing **URL:** \ **Category:** Elasticsearch\ **Created:** [June 17, 2016, 4:58pm UTC](https://discuss.elastic.co/t/queue-capacity-sizing/53176 "2016-06-17T16:58:01Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\ **Post date:** [June 17, 2016, 4:58pm UTC](https://discuss.elastic.co/t/queue-capacity-sizing/53176/1 "2016-06-17T16:58:02Z")
I am receiving the below error. The node is running ES 2.3.3 ``` [9992]: index [bro-2016.06.17], type [dns], id [AVVfLgt-PuabKO2qHMAs], message [RemoteTransportException[[WORKER_NODE_7][10.1.55.14:9300][indices:data/write/bulk[s]]]; nested: RemoteTransportE xception[[WORKER_NODE_7][10.1.55.14:9300][indices:data/write/bulk[s][p]]]; nested: EsRejectedExecutionException[rejected execution of org.elasticsearch.transport.TransportService$4@ac859e6 on EsThreadPoolExecutor[bulk, queue capacity = 50, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@219eb920[Running, pool size = 16, active threads = 16, queued tasks = 114, completed tasks = 65446]]];] ``` Should I be increasing my threadpool size? I have a cluster of approx 12 data nodes and 10 client nodes and each of those client nodes are also running logstash. The node referenced in the error (the only one throwing such an error) currently has 32 gig of RAM and a 6TB HDD Any help would be appreciated ---
**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:** [June 18, 2016, 1:16am UTC](https://discuss.elastic.co/t/queue-capacity-sizing/53176/2 "2016-06-18T01:16:04Z")
> [@tgdesrochers](#): > > Should I be increasing my threadpool size? Ideally, no. Full threadpools are due to something else, so you need to find what that is. Are you measuring ES metrics, things like load, heap use, indexing/querying rates? ---
**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\ **Post date:** [June 18, 2016, 2:23am UTC](https://discuss.elastic.co/t/queue-capacity-sizing/53176/3 "2016-06-18T02:23:52Z")
I am using marvel for monitoring. The strange part is that it only effects this one node. I am wondering what I should be looking for to identify what is causing this. I use client nodes for all applications to connect to (logstash, kibana, etc) so I'm not sure why this one node (which is a data node) would be over whelmed with requests. Is there something I could provide which would help to identify the source of this error. ---
**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:** [June 18, 2016, 2:44am UTC](https://discuss.elastic.co/t/queue-capacity-sizing/53176/4 "2016-06-18T02:44:47Z")
Are you load balancing/round robin-ing the bulk requests? ---
**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\ **Post date:** [June 18, 2016, 12:51pm UTC](https://discuss.elastic.co/t/queue-capacity-sizing/53176/5 "2016-06-18T12:51:15Z")
Yes. In my logstash config the output lists 10 client nodes to use when ingesting data. Is there a specific option to enable to ensure they move from one to the next when they get a busy response. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:42pm UTC](https://discuss.elastic.co/t/queue-capacity-sizing/53176/6 "2017-07-05T22:42:33Z")