Deployment Architecture

Searchhead pooling and scheduled searches.

nocostk
Communicator

I'm running some tests with searchhead pooling and scheduled searches. I'm running a saved search every minute and the results are being sent from one search head only. They're only coming from the second search head when the first search head is down (restarted, etc.). My question is: how does Splunk determine which searchhead to run a scheduled search from? Is this configurable (round-robin, least connections, pegged to specific host, etc.)?

Tags (1)

ewoo
Splunk Employee
Splunk Employee

Are the clocks on your two search heads in sync?

0 Karma

Ledion_Bitincka
Splunk Employee
Splunk Employee

The search heads compete to run scheduled searches, thus there is no deterministic way of determining which search head will run a scheduled search (if at all). The workload should start to spread evenly across the search heads as the number of scheduled searches increases. Is there any reason that you're looking to configure on which search head a scheduled search runs?

Get Updates on the Splunk Community!

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...