Deployment Architecture

Splunk high availability failover and loadbalancers

aaronkorn
Splunk Employee
Splunk Employee

Hello,

We are setting up our splunk environment up with a loadbalancer with a failover search head and have found this article that discusses rsync to keep our search heads up to date together http://wiki.splunk.com/Community:HighAvailabilityAndSplunk.

A couple questions come up with this though...

1) Are there any other files that should be rsynced other than whats mentioned?
2) For certain .conf files that have a hashed password how do we overcome syncing these files and allowing the secondary instance to decrypt the passwords?
3) Would you even recommend using loadbalancers in this fashion with rysnc? If not, any alternatives/recommendations?
4) Any considerations that I may be missing?

Right now we have about 30 users on one search head but would like our deployment to be scalable and resilient.

Thanks for the help!

0 Karma

samhughe
Path Finder

Can't help with the other bits as we're running search head pooling ourselves but the shared secret part of the following link might be useful for point 2: http://wiki.splunk.com/Community:How_to_add_a_search_head_to_your_pool

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!

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...

Federated Search for Dynamic Data Self Storage Is Now Generally Available on Splunk ...

 Splunk is excited to announce the General Availability of Federated Search for Dynamic Data Self Storage ...

Index This | What has many keys but can’t unlock a door?

July 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...