# High Memory Consumption by Journald Causing Cluster Instability

## Problem

Journald seems to consume more than expected amount of memory causing cluster nodes instability.

## Environment

* Centos, RedHat - v7+

## Cause

* The `systemd` journal is configured by default to store logs only in a small ring-buffer in `_/run/log/journal_`, which is not persistent.
* Systemd-journald on some linux distros is configured to auto-detect which storage system to use for journal files, "volatile" or "persistent". The *`/var/log/journal`* file is not created by default, so the in-memory (tmpfs) `_/run/log/journal_` location is used. By default, it is configured to allow up to 4 GB of log data be stored. As a consequence, heavy journal activity can eat up memory to the default of 4 GB for the `_/run_` file system. For memory constrained environments, this can be significant

## Resolution

To limit the amount of in-memory logs stored in /run/log/journal, set the following in *`/etc/systemd/journald.conf`* :

{% tabs %}
{% tab title="Bash" %}

```bash
---

RuntimeMaxUse=500M

RuntimeMaxFileSize=10M

---
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://platform9.com/kb/pmk/solutions/high-memory-consumption-by-journald.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.