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!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...