# Why does the search active threads equal 0? **URL:** \ **Category:** Elasticsearch\ **Created:** [September 27, 2018, 8:57am UTC](https://discuss.elastic.co/t/why-does-the-search-active-threads-equal-0/150155 "2018-09-27T08:57:17Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![minhua1983](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@minhua1983](https://discuss.elastic.co/u/minhua1983)\ **Post date:** [September 27, 2018, 8:57am UTC](https://discuss.elastic.co/t/why-does-the-search-active-threads-equal-0/150155/1 "2018-09-27T08:57:17Z")
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. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 25, 2018, 8:59am UTC](https://discuss.elastic.co/t/why-does-the-search-active-threads-equal-0/150155/2 "2018-10-25T08:59:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.