Deployment Architecture

Search head clustering

neovenkat
Explorer

We have search head cluster with 3 SHs. The search head replication factor is set to 2. We are facing an issue when the scheduled reports are ran in the 3rd search head which does not have the replicated artifacts. Note this (3rd) search head was added to the cluster recently. Could please let us know if we are missing any configuration so that this issue does not occur

0 Karma

kartm2020
Communicator

Hi Neovenkat,

I think this is due to replication factor. Setting the replication in search head clustering is optional. I have the same environment as like yours. If you see below server.conf, i haven't set the rep factor.
Please remove rep factor and do the splunk restart and try again. I hope it will work.

server.conf:

[shclustering]
conf_deploy_fetch_url = https://XX.XX.XX.XX:8089
disabled = 0
mgmt_uri = https://XX.XX.XX.XX:8089
pass4SymmKey = *****
shcluster_label = shcluster1
id = ****

0 Karma
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!

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...