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!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

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 ...