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!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Rounding off the Splunk Dashboard Contest

What does a contest-winning Splunk dashboard look like? In this case, it isn't in a browser tab at all. It ...

A Four Part Event Series: AI + Observability: AI Agents, LLMs, Apps, & Infrastructure

AI + Observability: AI Agents, LLMs, Apps, & Infrastructure The rapid evolution of artificial intelligence ...