# Prevent Elasticsearch go to a "stuck" state after heavy requests in Kibana

**URL:** <https://discuss.elastic.co/t/prevent-elasticsearch-go-to-a-stuck-state-after-heavy-requests-in-kibana/160343>\
**Category:** Elasticsearch\
**Created:** [December 11, 2018, 10:13am UTC](https://discuss.elastic.co/t/prevent-elasticsearch-go-to-a-stuck-state-after-heavy-requests-in-kibana/160343 "2018-12-11T10:13:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Merclangrat](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@Merclangrat](https://discuss.elastic.co/u/Merclangrat)\
**Post date:** [December 11, 2018, 10:13am UTC](https://discuss.elastic.co/t/prevent-elasticsearch-go-to-a-stuck-state-after-heavy-requests-in-kibana/160343/1 "2018-12-11T10:13:59Z")

</div>

We use Elasticsearch and Kibana and have quite a lot of data (~1TB).

Sometimes our users send very heavy request using Kibana (search/aggregations through 500GB of data) and Elasticsearch stops working at all. Only restart helps, and then it takes time for cluster to rebuild properly.

Are there any options to restrict so heavy requests? I mean, timeouts or something like this - for example, Elasticsearch stops processing data after, e.g. 120 sec and returns what it has already processed.

It will really save a lot of our nerves 🙂

---

<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:** [January 8, 2019, 10:14am UTC](https://discuss.elastic.co/t/prevent-elasticsearch-go-to-a-stuck-state-after-heavy-requests-in-kibana/160343/2 "2019-01-08T10:14:00Z")

</div>

Closed on January 8, 2019, 10:14am UTC

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