# \[URGENT\] Elasticsearch 5.1.1 cluster consuming more index space

**URL:** <https://discuss.elastic.co/t/urgent-elasticsearch-5-1-1-cluster-consuming-more-index-space/71878>\
**Category:** Elasticsearch\
**Created:** [January 17, 2017, 4:04pm UTC](https://discuss.elastic.co/t/urgent-elasticsearch-5-1-1-cluster-consuming-more-index-space/71878 "2017-01-17T16:04:47Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\
**Post date:** [January 24, 2017, 11:37pm UTC](https://discuss.elastic.co/t/urgent-elasticsearch-5-1-1-cluster-consuming-more-index-space/71878/23 "2017-01-24T23:37:41Z")

</div>

@ash007

Were you performing any queries while this data was collected? Can you perform the same search a few times that took 82 seconds? Also, can you attach the search that you're performing?

---

<div class="post-metadata">

**Author:** ![ash007](https://avatars.discourse-cdn.com/v4/letter/a/ccd318/32.png) [@ash007](https://discuss.elastic.co/u/ash007)\
**Post date:** [January 24, 2017, 11:51pm UTC](https://discuss.elastic.co/t/urgent-elasticsearch-5-1-1-cluster-consuming-more-index-space/71878/24 "2017-01-24T23:51:50Z")

</div>

@pickypg, I wasn't performing any search at that time. I just restarted the test cluster.

This is the search i was performing on the main cluster which took 82 seconds:  
curl -XGET "[http://localhost:9200/op-real-\*/\_search](http://localhost:9200/op-real-*/_search)" -v -d'  
{  
"query": {  
"match": {  
"message": "/open-service-locator/api/v2/"  
}  
}}'  
I performed the search few times and i am getting the results as the search data is being cached each time.

---

<div class="post-metadata">

**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\
**Post date:** [January 25, 2017, 12:01am UTC](https://discuss.elastic.co/t/urgent-elasticsearch-5-1-1-cluster-consuming-more-index-space/71878/25 "2017-01-25T00:01:14Z")

</div>

Elasticsearch does not cache queries unless `"size": 0`, but it would cache filters.

The only caching in play here would be the file system cache. If your performance was 82s without the file system cache for a regular query, then I have to wonder what is going on with the machine that is hosting the ES node.

---

<div class="post-metadata">

**Author:** ![ash007](https://avatars.discourse-cdn.com/v4/letter/a/ccd318/32.png) [@ash007](https://discuss.elastic.co/u/ash007)\
**Post date:** [January 25, 2017, 12:45am UTC](https://discuss.elastic.co/t/urgent-elasticsearch-5-1-1-cluster-consuming-more-index-space/71878/26 "2017-01-25T00:45:59Z")

</div>

@pickypg, my bad, i meant kibana was caching the results and providing them as i made same search multiple times from kibana.  
If i perform the same search on ES:  
first run took 89670 ms  
second run took 140794 ms  
third run took 107788 ms  
fourth run took 140407 ms  
fifth run took 98779 ms  
I am hosting ES nodes on centos aws ec2 m4.large machines with 200 GB of EBS volumes attached. Currently the storage is 54% full.

---

<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:** [February 22, 2017, 12:46am UTC](https://discuss.elastic.co/t/urgent-elasticsearch-5-1-1-cluster-consuming-more-index-space/71878/27 "2017-02-22T00:46:26Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/urgent-elasticsearch-5-1-1-cluster-consuming-more-index-space/71878.md?page=1)