# Set limits on Elasticsearch & Kibana

**URL:** <https://discuss.elastic.co/t/set-limits-on-elasticsearch-kibana/167070>\
**Category:** Elasticsearch\
**Created:** [February 5, 2019, 7:44am UTC](https://discuss.elastic.co/t/set-limits-on-elasticsearch-kibana/167070 "2019-02-05T07:44:39Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![gavenkoa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gavenkoa/32/23899_2.png) [@gavenkoa](https://discuss.elastic.co/u/gavenkoa)\
**Post date:** [February 12, 2019, 2:59pm UTC](https://discuss.elastic.co/t/set-limits-on-elasticsearch-kibana/167070/11 "2019-02-12T14:59:47Z")

</div>

@RdrgPorto We are experienced same problem with 30 sec limit in Kibana at about 60-80GB of indexes. And not we are at 150GB ))

My details:

> [@Kibana says "Error: Request Timeout after 30000ms" when we started to retain longer history in ES](https://discuss.elastic.co/t/kibana-says-error-request-timeout-after-30000ms-when-we-started-to-retain-longer-history-in-es/168050):
>
> I provide details below, straight to the point: I suspect that increased index count made impossible to perform some Kibana built-in queries. ls elasticsearch-5.6.14.deb kibana-5.6.14-amd64.deb I suspect that it is impossible to query 144GB of indexes on HDD with 4GB ES heap + 3GB mmap RAM: GET /\_nodes/stats/jvm "\_nodes": { "total": 1, "successful": 1, "failed": 0 }, ... "nodes": { "Tko1n5etQrmMvEm5viBBew": { "timestamp": 1549977948232, "name": "prod-es-1…

I can tell you one trick that sometimes helps. If your search query contains very frequent stem it won't work on large data.

For example instead of `"BLABLA has the problem"`to avoid 30000ms issue I search: `"BLABLA * problem"`

---

_[View the full topic](https://discuss.elastic.co/t/set-limits-on-elasticsearch-kibana/167070)._