Configure peer nodes with server.conf
Before reading this topic, see Configure the indexer cluster with server.conf. It discusses configuration issues that are common to all cluster node types.
Enable a peer node
The following example shows the basic settings that you must configure when enabling a peer node. The configuration attributes shown in these examples correspond to fields on the Enable clustering page of Splunk Web.
[replication_port://9887] [clustering] manager_uri = https://10.152.31.202:8089 mode = peer pass4SymmKey = whatever
This example specifies that:
- the peer will use port 9887 to listen for replicated data streamed from the other peers. You can specify any available, unused port as the replication port. Do not re-use the management or receiving ports.
- the peer's manager node resides at
- the instance is a peer node.
- the security key is "whatever".
You must restart the instance for the settings to take effect.
Edit the peer settings
You can change these settings later, if necessary. For example, to change the cluster's security key, you change the
pass4SymmKey value on each node.
Configure peer nodes with the dashboard
Configure peer nodes with the CLI
This documentation applies to the following versions of Splunk® Enterprise: 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.1.0, 9.1.1, 9.1.2