Acceldata
 Pulse
Search documentation… ⌘K

Manage Elasticsearch Disk Utilization

Issue

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

$AcceloHome/data/elasticsearch/nodes/0/indices
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:

du -hsx * | sort -rh | head -n 20
Sample output:

256G f8P9LtYASoaPJTxU-Y_1IQ
248G iLKFUc85T0OtYqpPCrBfBA
247G 9FnLtwknS36HGsjibmUGQg

Immediate Resolution: Identify and Delete Large Elasticsearch Indices

Step 1: List Elasticsearch Indices

Run the following command to identify large indices:

curl -X GET http://pulse:data%40ops@localhost:19013/_cat/indices
Example output:

green open edl-nifi-prod1-nifi-2026.05.04 iLKFUc85T0OtYqpPCrBfBA 1 0 247.6gb
green open edl-nifi-prod1-nifi-2026.05.03 f8P9LtYASoaPJTxU-Y_1IQ 1 0 255.3gb

Step 2: Delete High Disk Utilization Indices

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

curl -X DELETE "http://pulse:data%40ops@localhost:19013/<INDEX_NAME>"
Example:

curl -X DELETE "http://pulse:data%40ops@localhost:19013/edl-nifi-prod1-nifi-2026.05.04"
curl -X DELETE "http://pulse:data%40ops@localhost:19013/edl-nifi-prod1-nifi-2026.05.03"

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%