Are long queues in management threadpool a problem?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Are long queues in management threadpool a problem?

Gavin Seng

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/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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Are long queues in management threadpool a problem?

Mark Walkom-2
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 <[hidden email]> wrote:

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/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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com.
For more options, visit 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8gZdfNWz2%2BvsjYh1msCs8ygwSDe%3DFJKZBEutnUtqQwLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Are long queues in management threadpool a problem?

Gavin Seng

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 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="eiUWoy2uJSwJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">seng....@...> wrote:

<a style="margin-left:1em;margin-right:1em" href="http://i.imgur.com/FCpqeLR.png" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fi.imgur.com%2FFCpqeLR.png\46sa\75D\46sntz\0751\46usg\75AFQjCNHeOxUTlCpy44DR5x_1e5wh1uDXjw';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fi.imgur.com%2FFCpqeLR.png\46sa\75D\46sntz\0751\46usg\75AFQjCNHeOxUTlCpy44DR5x_1e5wh1uDXjw';return true;">

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:
  * <a href="https://github.com/elastic/elasticsearch/issues/7318" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Felastic%2Felasticsearch%2Fissues%2F7318\46sa\75D\46sntz\0751\46usg\75AFQjCNGC8QNO15_X_40iBZNmc0HSH-qJ4g';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Felastic%2Felasticsearch%2Fissues%2F7318\46sa\75D\46sntz\0751\46usg\75AFQjCNGC8QNO15_X_40iBZNmc0HSH-qJ4g';return true;">https://github.com/elastic/elasticsearch/issues/7318
  * <a href="https://github.com/elastic/elasticsearch/issues/7916" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Felastic%2Felasticsearch%2Fissues%2F7916\46sa\75D\46sntz\0751\46usg\75AFQjCNFXl9uF0RV9Wi0wmpTm73CT8tJyng';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Felastic%2Felasticsearch%2Fissues%2F7916\46sa\75D\46sntz\0751\46usg\75AFQjCNFXl9uF0RV9Wi0wmpTm73CT8tJyng';return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="eiUWoy2uJSwJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">elasticsearc...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com?utm_medium\75email\46utm_source\75footer';return true;" onclick="this.href='https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com?utm_medium\75email\46utm_source\75footer';return true;">https://groups.google.com/d/msgid/elasticsearch/4d9ad1e4-1225-4c89-9c70-7f68abc983a5%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/optout';return true;" onclick="this.href='https://groups.google.com/d/optout';return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/03e2d087-9610-44fd-80f5-262aaa2d370a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.