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:
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 .
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 .
warkolm
(Mark Walkom)
March 13, 2015, 7:07pm
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 seng.gavin@gmail.com wrote:
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:
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 .
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?utm_medium=email&utm_source=footer
.
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 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 .
For more options, visit https://groups.google.com/d/optout .
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 <javascript:>>
wrote:
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:
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 <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?utm_medium=email&utm_source=footer
.
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 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 .
For more options, visit https://groups.google.com/d/optout .