Monitoring Splunk

With coldToFrozenScript, what is responsible for deleting the bucket?

dwaddle
SplunkTrust
SplunkTrust

When you specify a coldToFrozenScript in indexes.conf, what is responsible for deleting the cold bucket from the indexer's disc? (eg, is it your script, or does Splunk delete it once your script has done whatever it's gonna do?)

I would have assumed the script would be responsible, but the example of compressedExport.sh does not show it actually deleting the bucket's data from the disk.

Tags (1)
1 Solution

amrit
Splunk Employee
Splunk Employee

Splunkd will delete the bucket after running your coldToFrozenScript. Your script can delete the bucket if it wishes, and Splunkd will handle this case without errors, but the main reason for the script is to give you a chance to archive your data however you wish before the bucket is deleted.

View solution in original post

amrit
Splunk Employee
Splunk Employee

Splunkd will delete the bucket after running your coldToFrozenScript. Your script can delete the bucket if it wishes, and Splunkd will handle this case without errors, but the main reason for the script is to give you a chance to archive your data however you wish before the bucket is deleted.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...

Federated Search for Dynamic Data Self Storage Is Now Generally Available on Splunk ...

 Splunk is excited to announce the General Availability of Federated Search for Dynamic Data Self Storage ...

Index This | What has many keys but can’t unlock a door?

July 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...