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!

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...

New! Splunk Observability Search Enhancements for Splunk APM Services/Traces and ...

Regardless of where you are in Splunk Observability, you can search for relevant APM targets including service ...

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...