Splunk Search

Multiple Search Heads in a Cluster

hvandenb
Path Finder

We're setting up an Index Cluster with a Master Node. From the documentation it looks like the Cluster will take care of replicating data and configuration between the Indexers. However, we're also wanting to have multiple search heads that work with the cluster.

What have people used to setup the search heads behind a load balancer. Do we need to use shared storage for the search heads or is there better configuration?

0 Karma
1 Solution

martin_mueller
SplunkTrust
SplunkTrust
0 Karma

hvandenb
Path Finder

I remember seeing a press on conf2013 about this as well. Basically, only the knowledge items need to be shared on the search heads.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

@gkanapathy did mention something similar to that in his Architecting for Scale talk at .conf 2012, maybe he can shed some light on viable alternatives to search head pooling.

0 Karma

hvandenb
Path Finder

Thanks for the answer. I'd like to avoid using shared storage as this adds complexity. I heard that some folks rsync knowledge bundles between search heads. We don't plan on running scheduled searches on the search heads, but rather have a separate server for that.
Have you seen this as an option?

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!

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...