Monitoring Splunk

How to resolve this error: The minimum free disk space (5000MB) reached for /opt/splunk/var/run/splunk/dispatch. user=admin", concurrency_category="historical", concurrency_context="user_instance-wide", current_concurrency=0, concurrency_limit=5000



I had this error below:
search:262 - reason="Search not executed: Dispatch Manager: The minimum free disk space (5000MB) reached for /opt/splunk/var/run/splunk/dispatch. user=admin.", concurrency_category="historical", concurrency_context="user_instance-wide", current_concurrency=0, concurrency_limit=5000

I do not want to change the limit 5000MB.
I already had deleted some logs in /opt/splunk/var/log/splunk like metrics.log.* but it did not resolve the issue.
Also try the clean-dispatch command, and also deleted the files inside the /opt/splunk/var/run/splunk/dispatch.

Is there any suggestion you could share with me excluding the change the set limit of 5000MB?

0 Karma

Esteemed Legend

Best answer: redo your search head so that /opt/splunk/var is in its own disk volume so that nothing else can take up this space. Some people even go so var as to put /opt/splunk/var/run/dispatch into its own volume.

The next best answer: add more disk space to to the volume that contains the dispatch directory.

OK answer: Reduce the TTL for search artifacts so things auto-purge more quickly as described here:

The WORST answer: reduce this quota in Settings -> Server settings -> General settings -> Pause indexing if free disk space (in MB) falls below.

0 Karma

0 Karma


Can you check "Indexing: Indexes and volumes" page in monitoring console to get more details?
Also you can try to adjust no of concurrent searches in limits.conf

0 Karma


Hi p_gurav,

The search capability is disabled.
Also, can you specify which parameter/attribute in limits.conf should I adjust?

0 Karma
.conf21 CFS Extended through 5/20!

Don't miss your chance
to share your Splunk
wisdom in-person or
virtually at .conf21!

Call for Speakers has
been extended through
Thursday, 5/20!