# Thread Pools and Queues **URL:** \ **Category:** Elasticsearch\ **Created:** [March 24, 2014, 2:08pm UTC](https://discuss.elastic.co/t/thread-pools-and-queues/16564 "2014-03-24T14:08:37Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Pawel\_Mlynarczyk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pawel_mlynarczyk/32/1568_2.png) [@Pawel\_Mlynarczyk](https://discuss.elastic.co/u/Pawel_Mlynarczyk)\ **Post date:** [March 24, 2014, 2:08pm UTC](https://discuss.elastic.co/t/thread-pools-and-queues/16564/1 "2014-03-24T14:08:37Z")
There are many users working with the application. Some of them are online users, that should have their requests served in real time and some of them are workers that are preparing reports and their requests can wait. At the moment, all the requests arriving to elasticsearch are queued at the same queue and that sometimes results in online users not getting their request served as soon as possible or even getting rejected when the queue is full of workers' requests. That could be solved by adding separate Thread Pool and Queue for 'low priority search'. Same would apply for other operations (get, bulk etc). Are there any plans or any chance for this kind of feature being implemented in Elasticsearch? -- 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/14bb9a8c-5d74-4a0e-a155-1178ce2be25b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/14bb9a8c-5d74-4a0e-a155-1178ce2be25b%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:** [March 24, 2014, 2:17pm UTC](https://discuss.elastic.co/t/thread-pools-and-queues/16564/2 "2014-03-24T14:17:22Z")
You could set up a special node for "low priority" search, with "slim" thread pool settings, and forward client calls to it respectively. Jörg On Mon, Mar 24, 2014 at 3:08 PM, Paweł Młynarczyk [zwarios@gmail.com](mailto:zwarios@gmail.com) wrote: > There are many users working with the application. Some of them are online > users, that should have their requests served in real time and some of them > are workers that are preparing reports and their requests can wait. At the > moment, all the requests arriving to elasticsearch are queued at the same > queue and that sometimes results in online users not getting their request > served as soon as possible or even getting rejected when the queue is full > of workers' requests. That could be solved by adding separate Thread Pool > and Queue for 'low priority search'. Same would apply for other operations > (get, bulk etc). > > Are there any plans or any chance for this kind of feature being > implemented in Elasticsearch? > > -- -- 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/CAKdsXoGbX3rQ6HEU2pzSKYpQhkm6Pe%3Dke%2B7qDAj%3DL-DfyMfyDg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGbX3rQ6HEU2pzSKYpQhkm6Pe%3Dke%2B7qDAj%3DL-DfyMfyDg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Pawel\_Mlynarczyk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pawel_mlynarczyk/32/1568_2.png) [@Pawel\_Mlynarczyk](https://discuss.elastic.co/u/Pawel_Mlynarczyk)\ **Post date:** [March 25, 2014, 9:55am UTC](https://discuss.elastic.co/t/thread-pools-and-queues/16564/3 "2014-03-25T09:55:10Z")
Thank you for your answer. I did some tests and it appears that the lowest queue size between the data nodes is the effective one (as far as I am concerned the search requests are spread across all nodes with data) and queue sizes in non data nodes are ignored (I guess that it is not ignored but redirecting search requests to data nodes omits storing them in queue). So the given solution is not working. Or am I missing something? Paweł Młynarczyk W dniu poniedziałek, 24 marca 2014 15:17:22 UTC+1 użytkownik Jörg Prante napisał: > You could set up a special node for "low priority" search, with "slim" > thread pool settings, and forward client calls to it respectively. > > Jörg > > On Mon, Mar 24, 2014 at 3:08 PM, Paweł Młynarczyk \<[zwa...@gmail.com](mailto:zwa...@gmail.com)\ > > > wrote: > > > There are many users working with the application. Some of them are > > online users, that should have their requests served in real time and some > > of them are workers that are preparing reports and their requests can wait. > > At the moment, all the requests arriving to elasticsearch are queued at the > > same queue and that sometimes results in online users not getting their > > request served as soon as possible or even getting rejected when the queue > > is full of workers' requests. That could be solved by adding separate > > Thread Pool and Queue for 'low priority search'. Same would apply for other > > operations (get, bulk etc). > > > > Are there any plans or any chance for this kind of feature being > > implemented in Elasticsearch? > > > > -- -- 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/3bdf14af-b2c0-4153-9f49-c7f5ad737e11%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3bdf14af-b2c0-4153-9f49-c7f5ad737e11%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, 1:40am UTC](https://discuss.elastic.co/t/thread-pools-and-queues/16564/4 "2017-07-06T01:40:52Z")