# ELK suddenly colapsed

**URL:** <https://discuss.elastic.co/t/elk-suddenly-colapsed/48414>\
**Category:** Elasticsearch\
**Created:** [April 26, 2016, 10:36am UTC](https://discuss.elastic.co/t/elk-suddenly-colapsed/48414 "2016-04-26T10:36:09Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![rusty](https://avatars.discourse-cdn.com/v4/letter/r/f17d59/32.png) [@rusty](https://discuss.elastic.co/u/rusty)\
**Post date:** [April 26, 2016, 1:01pm UTC](https://discuss.elastic.co/t/elk-suddenly-colapsed/48414/4 "2016-04-26T13:01:58Z")

</div>

> [@Anderson](#):
>
> I will try to decrease replication in the evening, and check if it works better.

You can also can close unused indexes (their data become unavailable, but it would free up the memory)

> [@Anderson](#):
>
> Is there some way how I can check if we got too much index data and terms incexed ?

Run `curl -XGET "localhost:9200/_stats?pretty"` and get a look at `all - segments - memory_in_bytes`. Divide memory\_in\_bytes by number of nodes and you'll get rough estimation of memory consumption on each node.

For more details, please, follow these links: [topic1](https://discuss.elastic.co/t/segments-memory-in-bytes-excessively-large-with-allot-of-open-indices/40622), [topic2](https://discuss.elastic.co/t/segments-memory-in-bytes-goes-down-after-reduction-of-segments-restart/41258)

---

_[View the full topic](https://discuss.elastic.co/t/elk-suddenly-colapsed/48414)._