# Changing RAM/DISK for “logging-and-metrics” leads to an health issue

**URL:** <https://discuss.elastic.co/t/changing-ram-disk-for-logging-and-metrics-leads-to-an-health-issue/182250>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [May 22, 2019, 2:19pm UTC](https://discuss.elastic.co/t/changing-ram-disk-for-logging-and-metrics-leads-to-an-health-issue/182250 "2019-05-22T14:19:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![apaulsen](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@apaulsen](https://discuss.elastic.co/u/apaulsen)\
**Post date:** [May 22, 2019, 2:19pm UTC](https://discuss.elastic.co/t/changing-ram-disk-for-logging-and-metrics-leads-to-an-health-issue/182250/1 "2019-05-22T14:19:06Z")

</div>

We saw high memory pressure and disk usage on logging-and-metrics.

![10](https://us1.discourse-cdn.com/elastic/original/3X/0/8/08b4b0f9c3f8f652da75e896796d698149c7c934.png)

We've decided to increase RAM/Disk via UI, editing the DATA setting to 2GB and 64GB disk space.  
Intermediately we’ve got a split brain situation.

![11](https://us1.discourse-cdn.com/elastic/original/3X/c/4/c46b08b96678350520eb735d9ab4594c0ada7f8e.png)

We've restarted the deployment and got the following picture:

![12](https://us1.discourse-cdn.com/elastic/original/3X/5/0/505a92d63a43dfdadf551e1f71c3c21bf6e3a5b7.png)

**How to get rid of the old DATA\_DEFAULT (her in ZONE-3)?.**

TIA,  
Agnes

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [May 22, 2019, 3:06pm UTC](https://discuss.elastic.co/t/changing-ram-disk-for-logging-and-metrics-leads-to-an-health-issue/182250/2 "2019-05-22T15:06:13Z")

</div>

Normal steps are:

- Turn `system_owned` to `false` in the advanced editor (data section)
- Override the instance capacity for the "overwhelmed" node
  - (ensure you have sufficient capacity on the allocator first, eg put it into maint mode, move off other instances as needed to get enough space .. eg looks like 1GB would be sufficient here)
  - Later version of ECE let you use the UI (there would be three dots in the top right of the instance boxes after turning system owned off if so) ...
    - if not you have to use the API: [https://www.elastic.co/guide/en/cloud-enterprise/2.2/Clusters\_-](https://www.elastic.co/guide/en/cloud-enterprise/2.2/Clusters_-)_Elasticsearch_-_CRUD_-\_Configuration.html#set-es-cluster-instances-settings-overrides (you need `restart_after_update=true`)

- Now the cluster should recover. Then you can reapply the original "upscale plan" and it should work

---

<div class="post-metadata">

**Author:** ![apaulsen](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@apaulsen](https://discuss.elastic.co/u/apaulsen)\
**Post date:** [May 22, 2019, 7:00pm UTC](https://discuss.elastic.co/t/changing-ram-disk-for-logging-and-metrics-leads-to-an-health-issue/182250/3 "2019-05-22T19:00:04Z")

</div>

> [@Alex\_Piggott](#):
>
> - Turn `system_owned` to `false` in the advanced editor (data section)
> - Override the instance capacity for the "overwhelmed" node

Perfect! "logging-and-metrics" is back to normal mode with more memory and disk space.

( + I turned system\_owned afterwards back to true)

Thanks!!

---

<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:** [June 5, 2019, 7:00pm UTC](https://discuss.elastic.co/t/changing-ram-disk-for-logging-and-metrics-leads-to-an-health-issue/182250/4 "2019-06-05T19:00:06Z")

</div>

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