Getting Data In

2 node cluster master reporting single peer to search head when there are 2 indexers

sanjeewa_fernan
Engager

Have 2 node Indexer cluster with a separate cluster master instance and separate SH instance, however when the SH is configured, it only shows 1 peer in the cluster as per attachment alt text

Why would the cluster master report as 1 peer to the SH when it has 2 peers listed in cluster configuration ?

Cluster master reports replication and search factor OK. see below

Replication factor met
Search factor met
All data is searchable
Indexing Ready YES

indexer1 893F55F8-DC7F-4378-A826-8A027763AE1D default
Searchable YES
Status Up
Bucket Count=6391

indexer2 90619A93-5668-45CB-AE9B-AE05B1ED43EC default
Searchable YES
Status Up
Bucket Count=107

0 Karma
1 Solution

sanjeewa_fernan
Engager

Hi, found out there was an issue with the Firewall rule connecting the Clustered SH, when the FW rule was opened (8080/8089) it worked 🙂

View solution in original post

0 Karma

sanjeewa_fernan
Engager

Hi, found out there was an issue with the Firewall rule connecting the Clustered SH, when the FW rule was opened (8080/8089) it worked 🙂

0 Karma

esix_splunk
Splunk Employee
Splunk Employee

Where is your Search Head pointing? To the CM or to the Indexer? In a clustered configuration, your search heads should all point to the Cluster Master. The cluster master will then distribute the list of indexers for search.

MuS
SplunkTrust
SplunkTrust

Hi @sanjeewa_fernando,

just to let you know, that I deleted the duplicate question from the moderation queue.

cheers, MuS

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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

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