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!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...