We're running v1.1.0 in production right now. We have 15 nodes and 15
shards w/ 4 replicas (75 total).
Recently we've ran into some problems that seem to be caused by using all
of the available threads and completely filling the queue. This is a
portion of what we see in the log:
[action.search.type] [Kang the Conqueror]  Failed to execute
rejected execution (queue capacity 1000) on
My question is, is it safe to increase the thread pool and queue size as a
solution? Is it necessary to increase both? If my thoughts are correct,
increasing the size of the thread pool should increase the amount of
concurrent searches, which might eliminate the need for a larger queue?
There is plenty of CPU available on all of the machines when this happens.
Current settings are the default; which in our case is 72 for thread pool
size and 1000 queue size.
Does anyone have any suggestions on tweaking these settings? Any best
practices to following?
If this is not a proper solution what might be some alternatives?
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@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8f106018-0892-4dc2-a25a-b0722d6ae94c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.