Each Splunk search job produces artifacts (results, logs, metadata) stored under $SPLUNK_HOME/var/run/splunk/dispatch/<SID>. Excess artifacts raise the following message:
Dispatch Command: The number of search artifacts in the dispatch directory is higher than recommended (<count>, <warning threshold>) and could have an impact on search performance.
Remove excess search artifacts using the "splunk clean-dispatch" CLI command, and review artifact retention policies in limits.conf and savedsearches.conf.
You can also raise this warning threshold in limits.conf / dispatch_dir_warning_size. Learn more.
Defaults (can be adjusted in limits.conf): dispatch_dir_warning_size attribute (Default 5000).
If the directory keeps filling, it may indicate overly long job lifetimes, excessive scheduled or real-time searches, or stalled artifacts.
How to verify?
1. In splunkd.log check for warnings from DispatchReaper,
WARN DispatchReaper [ DispatchReaper] - The number of search artifacts in the dispatch directory is higher than recommended (count=9225, warning threshold=5000) and could have an impact on search performance.
Remove excess search artifacts using the "splunk clean-dispatch" CLI command, and review artifact retention policies in limits.conf and savedsearches.conf. You can also raise this warning threshold in limits.conf / dispatch_dir_warning_size.
2. In CLI
Use the following command to verify the number of files in the dispatch directory.
$SPLUNK_HOME/var/run/splunk/dispatch$ ls -ls | wc -l
3. Splunk Cloud UI:
Navigate to Activity > Jobs and filter on jobs with long TTLs or large artifact sizes.
4. Scheduler logs:
Review scheduler.log to see which saved searches are generating the most artifacts or overrunning TTL.
sourcetype=scheduler OR source="/scheduler.log" status="continued" | chart limit=0 count by app
limits.conf → [search] dispatch_dir_warning_size and ensure it matches your operational requirements.savedsearches.conf entries for dispatch.ttl; shorten or align lifetimes with the actual search schedules.Adjusting saved search TTL:
Splunk Web UI
dispatch.ttl field.CLI
$SPLUNK_HOME/etc/apps/<app_name>/local/savedsearches.conf.dispatch.ttl attribute to the new lifetime (e.g., a multiple of the schedule). The default is twice (2x) the scheduled period.dispatch.ttl is twice the scheduled period unless alert actions extend it.splunk cmd splunkd clean-dispatch to remove stale artifacts (examples provided below for Splunk Enterprise).Increase dispatch_dir_warning_size in limits.conf to a value that reflects the expected number of concurrent jobs, then restart Splunk or reload the configuration.
splunk cmd splunkd clean-dispatch /opt/splunk/old-dispatch-jobs/ -1month splunk cmd splunkd clean-dispatch /opt/splunk/old-dispatch-jobs/ -10d@d splunk cmd splunkd clean-dispatch /opt/splunk/old-dispatch-jobs/ 2011-06-01T12:34:56.000-07:00
Note: Raising the threshold only hides the alert; it does not remediate search-head performance issues caused by excessive artifacts.
dispatch.ttl defaults to twice the schedule interval unless overridden or extended by alert actions.Dispatch directory and search artifacts #File descriptions for search-specific directories
Dispatch directory maintenance
Extend job life times #Changing the default lifetime values
limits.conf
Manage search jobs
Too many search jobs found in the dispatch directory
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
28-Sep-2026
|
Initial Release |