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 and "Accept as Solution" 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 and "Accept as Solution" 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!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...