Deployment Architecture

filesystem full - now what?

a212830
Champion

Hi,

My splunk search-head/indexer filled up the filesystem that it was running on. When I try to login, it give me an error (out of space). I wanted to reduce the size of certain indexers, to clean-up space. How can I do that without the gui? Anything else that I can delete?

Tags (1)
0 Karma

lguinn2
Legend

+1 to Martin's answer. Also, since you probably need to recover at least a little disk space for Splunk to restart -
You can examine the contents of the following directories and delete files:

Splunk's own logs: $SPLUNK_HOME/var/log/splunk

Search results for running searches, and saved search results: $SPLUNK_HOME/var/run/splunk/dispatch

Note that removing the saved search results may cause some users to need to re-run old searches; in some environments, this might not be a good idea.

Finally, you might think about setting your maximum index sizes so that the sum of all indexes cannot exceed your disk capacity.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

You can always edit indexes.conf to reduce index sizes, no UI required.

http://docs.splunk.com/Documentation/Splunk/latest/Admin/Indexesconf

I_am_Jeff
Communicator

My version in 4.3. I've used maxDataSizeMB option to limit sizes. If you are using different file systems for hot and cold indexes, as I am, homePath.maxDataSizeMB and coldPath.masDataSizeMB operate independently. My experience is it takes Splunk a while to clean house once you set these options and restart.

0 Karma
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 ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...