Deployment Architecture

How does Search Head Pooling behave with a level 7 load balancer?

Flynt
Splunk Employee
Splunk Employee

How will Splunk behave with search head pooling and a level 7 load balancer? Will the user need to re-authenticate whenever they are moved to another server in the pool for whatever reason? Is there a way to use the same authentication token across all servers in the pool?

1 Solution

DerekB
Splunk Employee
Splunk Employee

If a user is redirected to a different search head, then yes, they have to re-authenticate. Search heads in a pool do not share session state.

This applies both to Splunkweb sessions (UI) and to splunkd sessions (REST API, CLI, etc.).

This is as of 5.0.1.

View solution in original post

DerekB
Splunk Employee
Splunk Employee

If a user is redirected to a different search head, then yes, they have to re-authenticate. Search heads in a pool do not share session state.

This applies both to Splunkweb sessions (UI) and to splunkd sessions (REST API, CLI, etc.).

This is as of 5.0.1.

Get Updates on the Splunk Community!

AppDynamics Summer Webinars

This summer, our mighty AppDynamics team is cooking up some delicious content on YouTube Live to satiate your ...

SOCin’ it to you at Splunk University

Splunk University is expanding its instructor-led learning portfolio with dedicated Security tracks at .conf25 ...

Credit Card Data Protection & PCI Compliance with Splunk Edge Processor

Organizations handling credit card transactions know that PCI DSS compliance is both critical and complex. The ...