Monitoring Splunk

[Multiple Clusters] search not returning from new cluster

sylim_splunk
Splunk Employee
Splunk Employee

A standalone SH had 2 multiple indexer clusters configured as per the docs below, which has been working well a while until I added 3rd cluster.

https://docs.splunk.com/Documentation/Splunk/7.2.4/Indexer/Configuremulti-clustersearch

The searches appear working only across the existing 2 indexer clusters but the indexers from the 3rd cluster do not return any data.

[clustering]
mode = searchhead
master_uri = clustermaster:one, clustermaster:two, clustermaster:three

[clustermaster:three]
master_uri=https://SplunkMaster03.com:8089
pass4SymmKey=correctSecret

Please help.

Labels (2)
Tags (2)
0 Karma
1 Solution

sylim_splunk
Splunk Employee
Splunk Employee

Search.log in Search job inspector shows that searches were only dispatched to the 2 existing cluster indexers but not to the new indexers.

The search GUI shows the field name, splunk_server_group field shows that dmc_xxx groups. This means the deployment monitoring console, DMC is enabled on the search head. With DMC enabled on SH, only search peers that are members of the indexer group are searched by default. Because all searches that run on the monitoring console instance follow this behavior, non-monitoring console searches might have incomplete results.

"Do Not Use Production Search Head for DMC" which is also documented in the link below - Resolution: Switching to "standalone" next to "distributed" fixed the issue.

https://docs.splunk.com/Documentation/Splunk/7.2.4/DMC/WheretohostDMC

View solution in original post

sylim_splunk
Splunk Employee
Splunk Employee

Search.log in Search job inspector shows that searches were only dispatched to the 2 existing cluster indexers but not to the new indexers.

The search GUI shows the field name, splunk_server_group field shows that dmc_xxx groups. This means the deployment monitoring console, DMC is enabled on the search head. With DMC enabled on SH, only search peers that are members of the indexer group are searched by default. Because all searches that run on the monitoring console instance follow this behavior, non-monitoring console searches might have incomplete results.

"Do Not Use Production Search Head for DMC" which is also documented in the link below - Resolution: Switching to "standalone" next to "distributed" fixed the issue.

https://docs.splunk.com/Documentation/Splunk/7.2.4/DMC/WheretohostDMC

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!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...