Deployment Architecture

How to resolve the indexer file system from reaching the threshold on ?

Koushik_Katta
Explorer

Indexer is filled up , i have got the retention policy accoridngly

Tags (1)
0 Karma

woodcock
Esteemed Legend

You are corrrect:
http://docs.splunk.com/Documentation/Splunk/6.5.1/Indexer/Configureindexstoragesize#Configure_index_...

And you need maxVolumeDataSizeMB; set it to whatever will make your filesystem X% full and then restart splunk.

As far as where, if this is a global maximum for the whole indexer then put it in a [default] stanza in .../etc/system/local. Othewise, go app, by app, index by index. The file is indexes.conf.

woodcock
Esteemed Legend

If you push this app out by DS, you need to make sure that it has restart splunkd set or it will not take effect. If you push it out manually, then you need to restart splunk yourself.

0 Karma

alacercogitatus
SplunkTrust
SplunkTrust

@Koushik_Katta Almost - the config is being pushed by DS in a non-clustered environment, yes? So the maxVolumeDataSizeMB needs to be set in HSY-ADMIN-all_indexers/local/indexes.conf, and re-deployed by the DS. IIRC the indexers under /splogs are set at 10TB ea, so maxVolumeDataSizeMB should be 8192000 ( 8 TB / 10 TB, yeah? ) Again - based off of memory - but should be close.

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