# Default search timeout not applying on search and msearch calls

**URL:** <https://discuss.elastic.co/t/default-search-timeout-not-applying-on-search-and-msearch-calls/198060>\
**Category:** Elasticsearch\
**Created:** [September 4, 2019, 2:03pm UTC](https://discuss.elastic.co/t/default-search-timeout-not-applying-on-search-and-msearch-calls/198060 "2019-09-04T14:03:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![o1o1o11o1](https://avatars.discourse-cdn.com/v4/letter/o/74df32/32.png) [@o1o1o11o1](https://discuss.elastic.co/u/o1o1o11o1)\
**Post date:** [September 4, 2019, 2:03pm UTC](https://discuss.elastic.co/t/default-search-timeout-not-applying-on-search-and-msearch-calls/198060/1 "2019-09-04T14:03:09Z")

</div>

I've configured ES 7.1 with a `default_search_timeout` of 120s, however when I list all search or msearch tasks (\*search) I can still see long running tasks of more than 20,000 seconds. I can cancel them just fine, but was wondering why does that happen. In all cases those tasks were coming from Kibana dashboards.

```
"search" : {
  "default_search_timeout" : "120s",
  "max_buckets" : "20000"
}
```

---

<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:** [October 2, 2019, 2:03pm UTC](https://discuss.elastic.co/t/default-search-timeout-not-applying-on-search-and-msearch-calls/198060/2 "2019-10-02T14:03:16Z")

</div>

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