Splunk® Enterprise

Managing Indexers and Clusters of Indexers

Splunk Enterprise version 7.2 is no longer supported as of April 30, 2021. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk® Enterprise. For documentation on the most recent version, go to the latest release.

Configure the master with server.conf

Prerequisites

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 the master node

The following example shows the basic settings that you configure when enabling a master node. Unless otherwise noted, the settings are required. The configuration attributes correspond to fields on the Enable clustering page of Splunk Web.

[clustering]
mode = master
replication_factor = 4
search_factor = 3
pass4SymmKey = whatever
cluster_label = cluster1

This example specifies that:

  • the instance is a cluster master node.
  • the cluster's replication factor is 4.
  • the cluster's search factor is 3.
  • the security key is "whatever". All nodes in the cluster use the same security key. See Configure the security key.
  • the cluster label is "cluster1." The optional cluster label is useful for identifying the cluster in the monitoring console. See Set cluster labels in Monitoring Splunk Enterprise. You set this attribute on the master node only.

Important: When the master 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 master while it is waiting for the peers to join the cluster. If you do, you will need to restart the peers a second time.

Note: When you enable the master node in Splunk Web, the resulting server.conf stanza includes attributes only for non-default values. For example, if you accept the default replication factor of 3 and do not enter a new value for it, the resulting stanza does not include the replication_factor attribute.

Edit the master settings

You can change these settings later, if necessary. For example, to change the cluster's security key, you edit the pass4SymmKey value on each node.

For details on all cluster attributes, including some advanced ones that rarely require editing, read the server.conf specification.

Last modified on 15 September, 2020
Configure the master with the dashboard   Configure the master with the CLI

This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters