# Elastic Search Memory Alert

**URL:** https://discuss.elastic.co/t/elastic-search-memory-alert/171066
**Category:** Elasticsearch
**Created:** [March 6, 2019, 9:44am UTC](https://discuss.elastic.co/t/elastic-search-memory-alert/171066 "2019-03-06T09:44:16Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![surajdalvi](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@surajdalvi](https://discuss.elastic.co/u/surajdalvi)
#### Post date: [March 6, 2019, 9:44am UTC](https://discuss.elastic.co/t/elastic-search-memory-alert/171066/1 "2019-03-06T09:44:16Z")

</div>

Hi there,

With respect to [https://discuss.elastic.co/t/elastic-search-heap-alert/155479](https://discuss.elastic.co/t/elastic-search-heap-alert/155479) I have updated the Elasticsearch mapping. Currently, I have 1 index with 5 shards and 1 replica. Still, I am getting the following memory alert continuously.

> You Elastic cloud cluster Memory usage is more than 70%.

@Christian_Dahlqvist, @dadoonet is my cluster working properly because I am getting this alert continuously

may I know the all possible reasons for this error and how I can solve this?

---

<div class="post-metadata">

### Author: ![surajdalvi](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@surajdalvi](https://discuss.elastic.co/u/surajdalvi)
#### Post date: [March 12, 2019, 4:58am UTC](https://discuss.elastic.co/t/elastic-search-memory-alert/171066/2 "2019-03-12T04:58:37Z")

</div>

@Christian_Dahlqvist, @dadoonet is my cluster working properly because I am getting this alert continuously

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [March 12, 2019, 8:28am UTC](https://discuss.elastic.co/t/elastic-search-memory-alert/171066/3 "2019-03-12T08:28:53Z")

</div>

It sounds like you could benefit from a larger heap, but without more information around the use case, data and queries it is hard to tell.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [March 12, 2019, 10:26am UTC](https://discuss.elastic.co/t/elastic-search-memory-alert/171066/4 "2019-03-12T10:26:31Z")

</div>

May be ask the cloud support if this is expected?

Please see [https://www.elastic.co/cloud/as-a-service/support](https://www.elastic.co/cloud/as-a-service/support) on how to raise a support ticket for Elastic Cloud 🙂

---

<div class="post-metadata">

### Author: ![surajdalvi](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@surajdalvi](https://discuss.elastic.co/u/surajdalvi)
#### Post date: [March 13, 2019, 6:06am UTC](https://discuss.elastic.co/t/elastic-search-memory-alert/171066/5 "2019-03-13T06:06:22Z")

</div>

Hi, @Christian_Dahlqvist I am having 8GB Ram and my data size is 25GB. Currently, I am having 235GB Disk Available. I am using the following type of query on elastic search:

- Create Document
- Update Document
- Delete Document
- Delete By Query
- Update By Query
- Get Document
- Get All Documents

Does this cause a larger heap issue?

---

<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: [April 10, 2019, 6:06am UTC](https://discuss.elastic.co/t/elastic-search-memory-alert/171066/6 "2019-04-10T06:06:25Z")

</div>

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