We are running DM acceleration, we saw that every time the acceleration is running the disk got full.
After investigation, we saw that the data of the old guid does not removed from disk and that cause our disk full.
We are running Splunk using Docker image and using ansible. looks like it is an issue with ansible but im not sure.
Any idea anyone ?
DM acceleration summary files are kept in indexers by using guid of the search head that has DM config. If you are starting a fresh Splunk Docker image every time, this guid will change and re-create a new acceleration files.
You should run Splunk by keeping /opt/splunk/etc path persistent on disk. This will prevent changing guid and also new summary files.