Configure the manager node 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 indexer cluster configuration with the CLI. It provides details on issues that are common to all cluster node types.
Enable the manager node
The following example shows the basic settings that you typically configure when enabling a manager node. The configuration attributes correspond to fields on the Enable clustering page of Splunk Web.
splunk edit cluster-config -mode manager -replication_factor 4 -search_factor 3 -secret your_key -cluster_label cluster1 splunk restart
-secret flag modifies the
pass4SymmKey setting in the
[clustering] stanza of
When the manager node starts up for the first time, it will block indexing on the peers until you enable and restart the full replication factor number of peers. Do not restart the manager while it is waiting for the peers to join the cluster. If you do, you will need to restart the peers a second time.
Edit the manager node settings
You can also use the CLI to edit the configuration later. Use the
splunk edit cluster-config command, the same command used to enable the manager initially.
Refer to the CLI clustering help, along with the server.conf specification file, for the list of configurable settings.
Warning: Do not increase the replication factor or search factor on the manager node
Although it is possible to change the settings for the replication factor and search factor, it is inadvisable to increase either of them after your cluster contains significant amounts of data. Doing so will kick off a great deal of bucket activity, which will have an adverse effect on the cluster's performance while bucket copies are being created or made searchable.
Configure the manager node with server.conf
Replace the manager node on the indexer cluster
This documentation applies to the following versions of Splunk® Enterprise: 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.2.0, 8.2.1, 8.2.2