Hi, Look at query rates and see if they correlate. I'm guessing they jumped, too. SPM <http://sematext.com/spm> will help with that. Once you confirm you can trace the source of queries further upstream.
Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/ On Saturday, November 22, 2014 12:51:31 AM UTC-5, Christopher Ambler wrote: > > Odd behavior - our 5-node cluster hums along happily but then, once or > twice a day, one node pops to all 1000 threads (the default limit) being > hit and the node becomes unresponsive, causing our whole cluster to become > extremely slow. > > Has anyone experienced this? Any good way to diagnose this? > > Memory and CPU appear normal, if that helps... I'm not even sure where to > start here. > -- 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/0e9816ce-63da-4143-a1fa-7f939d4fc657%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
