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!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...