Splunk Search

Dispatch Directory question

rmorlen
Splunk Employee
Splunk Employee

We keep getting the message: "WARN DispatchReaper - Too many search jobs found in the dispatch directory (found=3575, warning level=3500). This could negatively impact search starting times".

As you will notice we have already bumped the value to 3500. We can bump it again but would like to figure out what is a good value. Anyway to determine this?

Tags (1)
0 Karma

rmorlen
Splunk Employee
Splunk Employee

I created an alert that monitors for the message and then calls a script to clean the dispatch directory as necessary.

0 Karma

rmorlen
Splunk Employee
Splunk Employee

The only real issue is that users see the warnings.

0 Karma

linu1988
Champion

From my point of view the dispatch directory contains the run stats of the saved searches. If you can configure the values low then you will get rid of the alert. They are not much of a use. The dispatch directory only eats away the memory in the hard drive nothing else... Correct me if i am wrong. Thanks.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...