Splunk Enterprise

datamodel acceleration doesn't remove old guid

sarit_s
Communicator

Hello,
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 ?

Thanks

Labels (2)
Tags (2)
0 Karma

scelikok
SplunkTrust
SplunkTrust

Unfortunately no, only deleted by the search head if it disables/rebuilds the acceleration.

You should manually delete the old ones. 

If this reply helps you an upvote is appreciated.
0 Karma

scelikok
SplunkTrust
SplunkTrust

Hi @sarit_s,

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.

If this reply helps you an upvote is appreciated.
0 Karma

sarit_s
Communicator

Thanks!

what about that the old once kept on disk? Shouldnt they be removed once i have new once?

0 Karma
Get Updates on the Splunk Community!

Improve Your Security Posture

Watch NowImprove Your Security PostureCustomers are at the center of everything we do at Splunk and security ...

Maximize the Value from Microsoft Defender with Splunk

 Watch NowJoin Splunk and Sens Consulting for this Security Edition Tech TalkWho should attend:  Security ...

This Week's Community Digest - Splunk Community Happenings [6.27.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...