Hey! Your graphs are really nice. That looks like grafana. I was wondering how you're pipiing data there? I used the ES graphite plugin and found that it flooded my graphite with too much data.
Thanks On Wednesday, July 16, 2014 9:26:46 AM UTC+2, Klavs Klavsen wrote: > > I updated the graph: > http://blog.klavsen.info/ES-graphs-update.png > > I added overview of how many threads were running, and its appearent that > what peaked when it crashed (left side of the two graphs - two spikes where > it crashed) - correlated with a peak in search threads. > Also the change to G1GC for two of the nodes - is very appearent in the > heap_mem_usage graph :) > > It's been stable for two days now.. nearing the record :) I did also move > a "culprit" who searched the main index for larger periods, to their own > index.. and change threadpool.index.queue_size: from -1 to 900. > the index queue size does not seem to be hit at all, so I'm not sure that > made a change. > > Thank you for your input everyone. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ff6462a4-e99a-4b82-b45a-303a9c87c3bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
