# Adding timeout and allowPartialSearchResults to query not timing out as expected

**URL:** <https://discuss.elastic.co/t/adding-timeout-and-allowpartialsearchresults-to-query-not-timing-out-as-expected/231636>\
**Category:** Elasticsearch\
**Created:** [May 7, 2020, 11:20pm UTC](https://discuss.elastic.co/t/adding-timeout-and-allowpartialsearchresults-to-query-not-timing-out-as-expected/231636 "2020-05-07T23:20:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![BrianJenney](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brianjenney/32/60496_2.png) [@BrianJenney](https://discuss.elastic.co/u/BrianJenney)\
**Post date:** [May 7, 2020, 11:20pm UTC](https://discuss.elastic.co/t/adding-timeout-and-allowpartialsearchresults-to-query-not-timing-out-as-expected/231636/1 "2020-05-07T23:20:56Z")

</div>

Using elasticearch client for nodejs v7.5.2:

Adding a timeout to the query body like `{ "timeout": "1s" }` eventually times out long requests but it takes far longer than 1 second for the query to actually timeout.

In reality the query can run for more like 10 - 20 seconds before timing out. Is this timeout parameter not exactly enforced? Is there a better way to kill long running queries?

---

<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:** [June 4, 2020, 11:20pm UTC](https://discuss.elastic.co/t/adding-timeout-and-allowpartialsearchresults-to-query-not-timing-out-as-expected/231636/2 "2020-06-04T23:20:57Z")

</div>

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