Manage Elasticsearch Disk Utilization

Issue

You may observe that the Pulse data directory is filling up due to large Elasticsearch indices under:

Bash
Copy

In some cases, individual indices can consume hundreds of GBs, causing the disk utilization on the Pulse node to reach critical levels.

Symptoms

You may observe:

  • High disk utilization on the Pulse node
  • Elasticsearch indices consuming excessive storage
  • Pulse instability due to low available disk space

Example:

Bash
Copy

Sample output:

Bash
Copy

Immediate Resolution: Identify and Delete Large Elasticsearch Indices

Step 1: List Elasticsearch Indices

Run the following command to identify large indices:

Bash
Copy

Example output:

Bash
Copy

Step 2: Delete High Disk Utilization Indices

After identifying unnecessary or older large indices, delete them using:

Bash
Copy

Example:

Bash
Copy

Result

After deleting the large indices:

  • Disk utilization reduced significantly
  • Elasticsearch storage usage returned to stable levels

Example outcome:

  • Disk utilization reduced to approximately 56%
VariableType to search · ESC to discard
GlossaryType to search · ESC to discard
InsertType to search · ESC to discard
No matches