# Queue Size limited? **URL:** \ **Category:** Elasticsearch\ **Created:** [February 23, 2015, 8:40am UTC](https://discuss.elastic.co/t/queue-size-limited/22324 "2015-02-23T08:40:13Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Abid\_Hussain](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@Abid\_Hussain](https://discuss.elastic.co/u/Abid_Hussain)\ **Post date:** [February 23, 2015, 8:40am UTC](https://discuss.elastic.co/t/queue-size-limited/22324/1 "2015-02-23T08:40:13Z")
Hi all, last restart of our cluster caused a heavy load as a couple of rivers are triggered which load alltogether about 40 GB of data into the (single-node) cluster. This lead to massive exceptions like shown in the logs: [6726]: index [my\_index], type [my\_doc\_type], id [2390342], message [EsRejectedExecutionException[rejected execution (queue capacity 50) on org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1@4a94944]] We didn't change any of the threadpools queue size settings (like threadpool.bulk.queue\_size). AFAIK in this case the queue size is unlimited. So how is it possible that the exception above can occur? Why does the log message indicate a queue size of 50? Regards, Abid -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7f095b58-e471-43a7-9d20-d35dabd1a697%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7f095b58-e471-43a7-9d20-d35dabd1a697%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [February 23, 2015, 4:16pm UTC](https://discuss.elastic.co/t/queue-size-limited/22324/2 "2015-02-23T16:16:03Z")
Is this with JDBC river? If so, you can increase the number of bulk actions per request, to decrease the concurrent bulk actions, to remedy situations where many rivers are active. Jörg On Mon, Feb 23, 2015 at 9:40 AM, Abid Hussain [hussain@novacom.mygbiz.com](mailto:hussain@novacom.mygbiz.com) wrote: > Hi all, > > last restart of our cluster caused a heavy load as a couple of rivers are > triggered which load alltogether about 40 GB of data into the (single-node) > cluster. > > This lead to massive exceptions like shown in the logs: > [6726]: index [my\_index], type [my\_doc\_type], id [2390342], message > [EsRejectedExecutionException[rejected execution (queue capacity 50) on > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1@4a94944 > ]] > > We didn't change any of the threadpools queue size settings (like > threadpool.bulk.queue\_size). AFAIK in this case the queue size is > unlimited. > > So how is it possible that the exception above can occur? Why does the log > message indicate a queue size of 50? > > Regards, > > Abid > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/7f095b58-e471-43a7-9d20-d35dabd1a697%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7f095b58-e471-43a7-9d20-d35dabd1a697%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/7f095b58-e471-43a7-9d20-d35dabd1a697%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7f095b58-e471-43a7-9d20-d35dabd1a697%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE6wXT%2BstLnyadVxXvi0-pzycMn9Nfbjv7AR7eABjaw7Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoE6wXT%2BstLnyadVxXvi0-pzycMn9Nfbjv7AR7eABjaw7Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Abid\_Hussain](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@Abid\_Hussain](https://discuss.elastic.co/u/Abid_Hussain)\ **Post date:** [February 24, 2015, 3:19pm UTC](https://discuss.elastic.co/t/queue-size-limited/22324/3 "2015-02-24T15:19:25Z")
Yes it happened with jdbc river. Thanks for clarification. Am Montag, 23. Februar 2015 17:16:09 UTC+1 schrieb Jörg Prante: > Is this with JDBC river? If so, you can increase the number of bulk > actions per request, to decrease the concurrent bulk actions, to remedy > situations where many rivers are active. > > Jörg > > On Mon, Feb 23, 2015 at 9:40 AM, Abid Hussain \<[hus...@novacom.mygbiz.com](mailto:hus...@novacom.mygbiz.com) > \\> wrote: > > > Hi all, > > > > last restart of our cluster caused a heavy load as a couple of rivers are > > triggered which load alltogether about 40 GB of data into the (single-node) > > cluster. > > > > This lead to massive exceptions like shown in the logs: > > [6726]: index [my\_index], type [my\_doc\_type], id [2390342], message > > [EsRejectedExecutionException[rejected execution (queue capacity 50) on > > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1@4a94944]] > > > > We didn't change any of the threadpools queue size settings (like > > threadpool.bulk.queue\_size). AFAIK in this case the queue size is > > unlimited. > > > > So how is it possible that the exception above can occur? Why does the > > log message indicate a queue size of 50? > > > > Regards, > > > > Abid > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/7f095b58-e471-43a7-9d20-d35dabd1a697%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7f095b58-e471-43a7-9d20-d35dabd1a697%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/7f095b58-e471-43a7-9d20-d35dabd1a697%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7f095b58-e471-43a7-9d20-d35dabd1a697%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/b7edddf8-a619-4a3d-a25f-8f8a40af3e36%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b7edddf8-a619-4a3d-a25f-8f8a40af3e36%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:30am UTC](https://discuss.elastic.co/t/queue-size-limited/22324/4 "2017-07-06T00:30:29Z")