# Why does the search active threads equal 0 in kibana

**URL:** <https://discuss.elastic.co/t/why-does-the-search-active-threads-equal-0-in-kibana/151376>\
**Category:** Elasticsearch\
**Created:** [October 8, 2018, 2:29am UTC](https://discuss.elastic.co/t/why-does-the-search-active-threads-equal-0-in-kibana/151376 "2018-10-08T02:29:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![minhua1983](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@minhua1983](https://discuss.elastic.co/u/minhua1983)\
**Post date:** [October 8, 2018, 2:29am UTC](https://discuss.elastic.co/t/why-does-the-search-active-threads-equal-0-in-kibana/151376/1 "2018-10-08T02:29:05Z")

</div>

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?  
When I used kibana to check my dashboard, I got the error info below:

 ![QQ%E5%9B%BE%E7%89%8720180927162247](https://us1.discourse-cdn.com/elastic/original/3X/7/1/7157bbdc6dde9d49fdc60c61bc5badc3c2c3a9be.png)

My ec2 environment of elasticsearch bases on the info below:  
4 core cpu  
16G ram  
window 2008

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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 5, 2018, 2:29am UTC](https://discuss.elastic.co/t/why-does-the-search-active-threads-equal-0-in-kibana/151376/2 "2018-11-05T02:29:20Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
