I set the search queue capacity up to 2000 a few days ago.
Why does the search active threads equal 0 when the search queue is over than 2000?
My ec2 environment of elasticsearch bases on the info below:
4 core cpu
16G ram
window 2008
When I used kibana to check my dashboard, I got the error info below:
Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"es_rejected_execution_exception","reason":"rejected execution of org.elasticsearch.transport.TransportService$7@6d759090 on EsThreadPoolExecutor[search, queue capacity = 2000, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@20aceb46[Running, pool size = 7, active threads = 0, queued tasks = 2010, completed tasks = 14103311]]"},{"type":"es_rejected_execution_exception","reason":"rejected execution of org.elasticsearch.transport.TransportService$7@7982b906 on EsThreadPoolExecutor[search, queue capacity = 2000, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@20aceb46[Running, pool size = 7, active threads = 0, queued tasks = 2011, completed tasks = 14103311]]"},{"type":"es_rejected_execution_exception","reason":"rejected execution of org.elasticsearch.transport.TransportService$7@4ae6f8f2 on EsThreadPoolExecutor[search, queue capacity = 2000, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@20aceb46[Running, pool size = 7, active threads = 0, queued tasks = 2012, completed tasks = 14103311]]"},{"type":"es_rejected_execution_exception","reason":"rejected execution of org.elasticsearch.transport.TransportService$7@49a53e9a on EsThreadPoolExecutor[search, queue capacity = 2000, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@20aceb46[Running, pool size = 7, active threads = 0, queued tasks = 2013, completed tasks = 14103311]]"}.....
The frequency of this issue above is not at a high level.
There are several visualizes in my dashboard. Each of them set an aggregation at least. I have no idea what caused this issue.