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!

Message Parsing in SOCK

Introduction This blog post is part of an ongoing series on SOCK enablement. In this blog post, I will write ...

Exploring the OpenTelemetry Collector’s Kubernetes annotation-based discovery

We’ve already explored a few topics around observability in a Kubernetes environment -- Common Failures in a ...

Use ‘em or lose ‘em | Splunk training units do expire

Whether it’s hummus, a ham sandwich, or a human, almost everything in this world has an expiration date. And, ...