Cluster Master is not disabled after removal of the 'Cluster Master' server role in DMC

Available Languages

Updated:September 29, 2026

Document ID:SPLK046330

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Enterprise

Description

The Cluster Manager is not disabled after the removal of the Cluster Master server role in DMC because the [clustering] mode setting is not updated inserver.conf.

The below message keeps coming up in Splunk Web messages because the CM is not disabled:

Search peer x.x.x.x has the following message:
Waiting for requisite number of peers to join the cluster. 
https://x.x.x.x:8089. site=site1 has only 0 peers 
(waiting for 1 peers to join the site). site=site2 has only 0 peers (waiting for 1 peers to join the site).

Investigation

Both servers are reporting the warning because it was having the manager role and the error message is coming up because it was expecting the requisite number of peers to connect.

Resolution

Here are the steps to disable the CM:

1. Edit $SPLUNK_HOME/etc/system/local/server.conf with the settings:

[clustering] 
mode = disabled

2. Restart Splunk.

Revision History

Revision	Publish Date	Comments
1.0	29-Sep-2026	Initial Release

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)

This Document Applies to These Products

Splunk Enterprise