Getting Data In

Reduce clustered index COLD which becomes oversized over time

splunkreal
Influencer

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
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!

Cisco Data Fabric from Architecture to Investigation, Better SOC Visibility, and More ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

The Trust Gap: Why a Data Foundation is Fundamental to an Agentic Enterprise

The Trust Gap: Why a data foundation is fundamental to an  Agentic Enterprise.   Agentic AI is transforming ...

Data Management Digest – September 2026

    Welcome to the September 2026 edition of Data Management Digest! September brought a fresh wave of ...