Configure peer nodes with the CLI
Read this first
Before reading this topic, see:
- Configure and manage the indexer cluster with the CLI. This topic explains the basics of cluster configuration with the CLI. It provides details on issues that are common to all indexer cluster node types.
Enable a peer node
The following example shows the basic settings that you typically configure when enabling a peer node. The configuration attributes correspond to fields on the Enable clustering page of Splunk Web.
To enable an instance as a peer node, set mode
to "peer". You also need to specify manager_uri
, which specifies the cluster's manager node, and replication_port
. In addition, you must specify the cluster-wide security key (secret
):
splunk edit cluster-config -mode peer -manager_uri https://10.160.31.200:8089 -replication_port 9887 -secret your_key splunk restart
The -secret
flag modifies the pass4SymmKey
setting in the [clustering]
stanza of server.conf
.
Edit the peer settings
You can also use the CLI to edit the configuration later. Use the splunk edit cluster-config
command, the same command that you use to enable the peer initially.
Refer to the CLI clustering help, along with the server.conf specification file, for the list of configurable settings.
Configure peer nodes with server.conf | Manage common configurations across all peers |
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.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.1.7, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.3.0, 9.3.1, 9.3.2, 9.4.0
Feedback submitted, thanks!