Deployment Architecture

Search Head Pooling - Shared Storage Not Available

Edub
Explorer

I am setting up search head pooling in a geographically diverse implementation. I have indexes and search heads in 3 different cities. All the Splunk units have access to each other over high speed links.

I want to pool the search heads for HA and load management, but do not have a way to give them shared storage. It is not that difficult to make storage at one site available to the others, but if that storage is unavailable, then our search head HA is busted.

I really need search head pooling without the use of shared storage. Could the search heads share info directly with each other instead of writing to shared storage?

What other ways are there to enable search head pooling?


Tags (2)
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

In 4.2, search head pooling requires shared storage to work.

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

In 4.2, search head pooling requires shared storage to work.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...