Getting Data In

Why are 50% of saved searches and scheduled searches showing as skipped on my Windows search heads?

brod_geico
Path Finder

On my windows search heads some of the searches showing skipped status. Some of them are running and some of them are not.
status=skipped, scheduled_time=1418934000.

i have checked below things.
disk quota limit.
alerts conf files
dispatcher

DispatchManager - The system is approaching the maximum number of historical searches that can be run concurrently. current=12 maximum=14
12-18-2014 14:36:04.542 -0500 WARN DispatchManager - The system is approaching the maximum number of historical searches that can be run concurrently. current=12 maximum=14
12-18-2014 14:36:11.979 -0500 WARN DispatchManager - The system is approaching the maximum number of historical searches that can be run concurrently. current=12 maximum=14
12-18-2014 14:36:19.401 -0500 WARN DispatchManager - The system is approaching the maximum number of historical searches that can be run concurrently. current=12 maximum=14

The system is approaching the maximum number of historical searches

0 Karma

jayannah
Builder

That's because adhoc searches are having higher priority over scheduled searches.

How many CPU core in the search head and indexers in your configuration?

You may have increase number of search heads or CPU core since it looks high number of searches are running concurrently.

0 Karma

brod_geico
Path Finder

Thanks for your help i have checked that already. im running with spluk 6.1 verison

0 Karma

somesoni2
Revered Legend

I guess you're running more searches then your role allows you to run con-currently. Check this link to see how the quota is calculated.

http://wiki.splunk.com/Community:TroubleshootingSearchQuotas

0 Karma
Get Updates on the Splunk Community!

Technical Workshop Series: Splunk Data Management and SPL2 | Register here!

Hey, Splunk Community! Ready to take your data management skills to the next level? Join us for a 3-part ...

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...

Video | Tom’s Smartness Journey Continues

Remember Splunk Community member Tom Kopchak? If you caught the first episode of our Smartness interview ...