Getting Data In

Reduce clustered index COLD which becomes oversized over time

splunkreal
Motivator

Hello guys,

one clustered index is now oversized due to lower indexed data since several months and data froze over time.

The COLD size shows it only uses now 1 gb of ~4 gb so is it safe to reduce the COLD path and maxtotaldatasizemb? In my opinion it should have no effect on the index, it should not freeze current data?

Thanks for your help.

Enterprise 7.1.4

* If this helps, please upvote or accept solution if it solved *
Labels (1)
0 Karma
Get Updates on the Splunk Community!

What the End of Support for Splunk Add-on Builder Means for You

Hello Splunk Community! We want to share an important update regarding the future of the Splunk Add-on Builder ...

Solve, Learn, Repeat: New Puzzle Channel Now Live

Welcome to the Splunk Puzzle PlaygroundIf you are anything like me, you love to solve problems, and what ...

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...