I should probably preface everything with I'm running a 5 node cluster with version 0.19.3 and should be up to version 1.1.2 by the middle of August, but I have some confusion around metrics I'm seeing, what they mean and what are good values.
In thread_pools I see threads, active and queued. Queued + active != threads. I assume this really is a work pool and you have active threads, a thread count in the work pool and queued work. So some explanation around this would be nice. I've correlated some spikes in search threads with heap mem utilization explosions. current searches sort of also correlate, but I have more current searches than search threads and there is not search threadpool queueing. I'm not sure how current searches correlate (or if they should/do) with search threads. I've observed the following: Devestating: 10,000 current searches on worst index sustained over hours with not much change ending at the same time as spikes of > 1000 search threads (where we generally average < 50) and a heap explosion. Oddly OK: current searches averaging 15 on worst index spiking to 105 with search threads averaging 50 with maxes of 300 spiking to averages of 120 and maxes of > 1000 So... I guess, what are good ranges for search threads and current searches? --Shannon Monasco -- 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/8723911c-f764-4286-9f52-7750273a7610%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
