Deployment Architecture

Why do I need layer-7 load balancer in front of Splunk Search Head Cluster

xchang1226
Path Finder

We are trying to add a load balancer in front of our Splunk Search Head Cluster (SHC), according to the official doc, we need layer-7/application level load balancer which provides session stickiness. The thing I don't quite understand is since SHC is doing replication across all members, why does user need to be on the same search head? We also have following in the web.conf to prevent logging user out due to session timeout. We are using SAML SSO, so user won't get a login screen even it times out. So does anyone know why we would need session stickiness?

tools.sessions.timeout = 3600
ui_inactivity_timeout = 0

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Without session stickiness users may see partial page loads and other strange behavior. Because SHC replication is not instant, users may be directed to a SH that does not have their KOs.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Without session stickiness users may see partial page loads and other strange behavior. Because SHC replication is not instant, users may be directed to a SH that does not have their KOs.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Index This | What did the zero say to the eight?

June 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...

Splunk Observability Cloud's AI Assistant in Action Series: Onboarding New Hires & ...

This is the fifth post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...

Now Playing: Splunk Education Summer Learning Premieres

It’s premiere season, and Splunk Education is rolling out new releases you won’t want to miss. Whether you’re ...