Installation Guide
Pulse 4.1.x
Overview
Prerequisites
Installation
Advanced Installation
Admin UI (K8S only)
Pulse Administration
Upgrade
Advanced Feature Integrations
Developer Tools
Troubleshooting
Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Manage Elasticsearch Disk Utilization
Summarize Page
Copy Markdown
Open in ChatGPT
Open in Claude
Connect to Cursor
Connect to VS Code
Issue
You may observe that the Pulse data directory is filling up due to large Elasticsearch indices under:
Bash
xxxxxxxxxx$AcceloHome/data/elasticsearch/nodes/0/indicesIn 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
xxxxxxxxxxdu -hsx * | sort -rh | head -n 20Sample output:
Bash
xxxxxxxxxx256G f8P9LtYASoaPJTxU-Y_1IQ248G iLKFUc85T0OtYqpPCrBfBA247G 9FnLtwknS36HGsjibmUGQgImmediate Resolution: Identify and Delete Large Elasticsearch Indices
Step 1: List Elasticsearch Indices
Run the following command to identify large indices:
Bash
xxxxxxxxxxcurl -X GET http://pulse:data%40ops@localhost:19013/_cat/indicesExample output:
Bash
xxxxxxxxxxgreen open edl-nifi-prod1-nifi-2026.05.04 iLKFUc85T0OtYqpPCrBfBA 1 0 247.6gbgreen open edl-nifi-prod1-nifi-2026.05.03 f8P9LtYASoaPJTxU-Y_1IQ 1 0 255.3gbStep 2: Delete High Disk Utilization Indices
After identifying unnecessary or older large indices, delete them using:
Bash
xxxxxxxxxxcurl -X DELETE "http://pulse:data%40ops@localhost:19013/<INDEX_NAME>"Example:
Bash
xxxxxxxxxxcurl -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%
VariableType to search · ESC to discard
GlossaryType to search · ESC to discard
InsertType to search · ESC to discard
No matches
Last updated on
Was this page helpful?
Next to read:
Disaster Recovery Strategy for MongoDB and VictoriaDBFor additional help, contact www.acceldata.force.com OR call our service desk +1 844 9433282
Copyright © 2026
Discard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message