# Are long queues in management threadpool a problem?

**URL:** https://discuss.elastic.co/t/are-long-queues-in-management-threadpool-a-problem/22643
**Category:** Elasticsearch
**Created:** [March 12, 2015, 8:23pm UTC](https://discuss.elastic.co/t/are-long-queues-in-management-threadpool-a-problem/22643 "2015-03-12T20:23:01Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Gavin\_Seng](https://avatars.discourse-cdn.com/v4/letter/g/e56c9b/32.png) [@Gavin\_Seng](https://discuss.elastic.co/u/Gavin_Seng)
#### Post date: [March 12, 2015, 8:23pm UTC](https://discuss.elastic.co/t/are-long-queues-in-management-threadpool-a-problem/22643/1 "2015-03-12T20:23:01Z")

</div>

[http://i.imgur.com/FCpqeLR.png](http://i.imgur.com/FCpqeLR.png)

Hi,

Has anyone experienced this issue? More importantly, is it a problem? We  
haven't seen anything bad ... but just in case this is an indicator.

- We are running 3 dedicated masters (Machine:4GB JVM:2GB CPU:2)
- Cluster
  - 3 masters
  - 4 data nodes
  - 2 tribe nodes
  - 9 logstash client nodes

- The 1 extra thing we're doing is curling every 10 min to "\_nodes/stats"  
and "\_cat/indices" (about 3K indices).
- Relevant issues regarding management threadpool:
  - [https://github.com/elastic/elasticsearch/issues/7318](https://github.com/elastic/elasticsearch/issues/7318)
  - [https://github.com/elastic/elasticsearch/issues/7916](https://github.com/elastic/elasticsearch/issues/7916)

Thanks in advance!

Gavin

--  
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/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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: [March 13, 2015, 7:07pm UTC](https://discuss.elastic.co/t/are-long-queues-in-management-threadpool-a-problem/22643/2 "2015-03-13T19:07:28Z")

</div>

As long as they don't stay too high then it's not a critical problem.

On 12 March 2015 at 13:23, Gavin Seng [seng.gavin@gmail.com](mailto:seng.gavin@gmail.com) wrote:

> [http://i.imgur.com/FCpqeLR.png](http://i.imgur.com/FCpqeLR.png)
> 
> Hi,
> 
> Has anyone experienced this issue? More importantly, is it a problem? We  
> haven't seen anything bad ... but just in case this is an indicator.
> 
> - We are running 3 dedicated masters (Machine:4GB JVM:2GB CPU:2)
> - Cluster
> - 3 masters
> - 4 data nodes
> - 2 tribe nodes
> - 9 logstash client nodes
> 
> - The 1 extra thing we're doing is curling every 10 min to "\_nodes/stats"  
> and "\_cat/indices" (about 3K indices).
> - Relevant issues regarding management threadpool:
> - [Internal: Management thread pool should reject requests when there are too many · Issue #7318 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/7318)
> - [Stats: \_status with #shards \>\> queue capacity failing with BroadcastShardOperationFailedException · Issue #7916 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/7916)
> 
> Thanks in advance!
> 
> Gavin
> 
> --  
> 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/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%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/CAEYi1X8gZdfNWz2%2BvsjYh1msCs8ygwSDe%3DFJKZBEutnUtqQwLw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8gZdfNWz2%2BvsjYh1msCs8ygwSDe%3DFJKZBEutnUtqQwLw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Gavin\_Seng](https://avatars.discourse-cdn.com/v4/letter/g/e56c9b/32.png) [@Gavin\_Seng](https://discuss.elastic.co/u/Gavin_Seng)
#### Post date: [March 14, 2015, 1:32am UTC](https://discuss.elastic.co/t/are-long-queues-in-management-threadpool-a-problem/22643/3 "2015-03-14T01:32:07Z")

</div>

Thanks Mark.

I guess I'm not sure what's considered too high ... 300 does seem kind of  
high ... in my mind I'm thinking that due to this the Master nodes might  
not have enough time to process cluster events (such as mapping updates,  
alias creations).

Gavin

On Friday, March 13, 2015 at 3:08:03 PM UTC-4, Mark Walkom wrote:

> As long as they don't stay too high then it's not a critical problem.
> 
> On 12 March 2015 at 13:23, Gavin Seng \<[seng....@gmail.com](mailto:seng....@gmail.com) \<javascript:\>\>  
> wrote:
> 
> > [http://i.imgur.com/FCpqeLR.png](http://i.imgur.com/FCpqeLR.png)
> > 
> > Hi,
> > 
> > Has anyone experienced this issue? More importantly, is it a problem? We  
> > haven't seen anything bad ... but just in case this is an indicator.
> > 
> > - We are running 3 dedicated masters (Machine:4GB JVM:2GB CPU:2)
> > - Cluster
> > - 3 masters
> > - 4 data nodes
> > - 2 tribe nodes
> > - 9 logstash client nodes
> > 
> > - The 1 extra thing we're doing is curling every 10 min to "\_nodes/stats"  
> > and "\_cat/indices" (about 3K indices).
> > - Relevant issues regarding management threadpool:
> > - [Internal: Management thread pool should reject requests when there are too many · Issue #7318 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/7318)
> > - [Stats: \_status with #shards \>\> queue capacity failing with BroadcastShardOperationFailedException · Issue #7916 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/7916)
> > 
> > Thanks in advance!
> > 
> > Gavin
> > 
> > --  
> > 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) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%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/03e2d087-9610-44fd-80f5-262aaa2d370a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/03e2d087-9610-44fd-80f5-262aaa2d370a%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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: [July 6, 2017, 12:26am UTC](https://discuss.elastic.co/t/are-long-queues-in-management-threadpool-a-problem/22643/4 "2017-07-06T00:26:49Z")

</div>


