Deployment Architecture

Why is Site Affinity not working with my current server.conf configuration on my search heads?

lycollicott
Motivator

I have this in server.conf on my search heads:

[general]
pass4SymmKey = $$$$$$$$$$$$$$$$$
serverName = xxx-xxxxxxxx
site = site1

[clustering]
master_uri = https://xx.xx.xx.xx:8089
mode = searchhead
multisite = true
pass4SymmKey = $$$$$$$$$$$$$$$$$

But my search results come from the splunk_server at sites1 and site2. Any idea why?

0 Karma
1 Solution

lycollicott
Motivator

Site affinity was actually working. The other site's splunk_server was only returning results for buckets which had not replicated.

Duh. Yes, I felt like an idiot.

View solution in original post

lycollicott
Motivator

Site affinity was actually working. The other site's splunk_server was only returning results for buckets which had not replicated.

Duh. Yes, I felt like an idiot.

s2_splunk
Splunk Employee
Splunk Employee

Is your cluster in site1 valid and complete, i.e. search and replication factors met and all peers up?

lycollicott
Motivator

Yes, it is valid and complete.

0 Karma
Get Updates on the Splunk Community!

Now Available: Cisco Talos Threat Intelligence Integrations for Splunk Security Cloud ...

At .conf24, we shared that we were in the process of integrating Cisco Talos threat intelligence into Splunk ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Easily Improve Agent Saturation with the Splunk Add-on for OpenTelemetry Collector

Agent Saturation What and Whys In application performance monitoring, saturation is defined as the total load ...