You configure indexes by editing the indexes.conf file. This file determines an indexer's set of indexes, as well as the size and attributes of its buckets. Since all peers in a cluster must use the same set of indexes (except for limited purposes, described later), the indexes.conf file should ordinarily be the same across all peers.
The cluster peers deploy with a peer-specific default indexes.conf file that handles basic cluster needs. If you want to add indexes or change bucket behavior, you edit a new indexes.conf file in a special location on the manager node and then distribute the file simultaneously to all the peers.
Important: You cannot use Splunk Web or the CLI to configure index settings on peer nodes. You must edit indexes.conf directly.
All peers must use the same set of indexes.conf files
The set of indexes.conf files should ordinarily be identical across all peers in a cluster. In particular, all peers must use the same set of clustered indexes. This is essential for index replication to work properly. (The manager node, on the other hand, has its own, separate indexes.conf file, because it indexes only its own internal data.) There is a limited exception to this restriction, which is described a bit later.
When you first create the cluster, the manager node distributes a special default indexes.conf file to each of the peers. This version supplements the standard default indexes.conf that all indexers get. The peer-specific default indexes.conf turns on replication for the main index, as well as the internal indexes, such as _audit and _internal.
Depending on your system, you might also need to edit and distribute a modified indexes.conf to the peers, to accommodate additional indexes or changes to bucket attributes. To ensure that all peers use the same indexes.conf, you must use the manager node to distribute the file to all the peers as a single process.This process, known as the configuration bundle method, is described in Update common peer configurations and apps.
You must also use the configuration bundle method to distribute apps across all the peers. These apps might contain their own indexes.conf files, which will layer appropriately with any non-app version of the file that you might also distribute to the peers. For information on app distribution, read Manage app deployment across all peers.
Note: Under limited circ*mstances (for example, to perform local testing or monitoring), you can create an indexes.conf for a single peer only. Such an index will not get replicated. The single-peer indexes.conf supplements, but does not replace, the common version of the file that all peers get. See Add an index to a single peer for details.
Configure a set of indexes for the peers
There are two steps to configuring indexes across the set of peers:
1. Edit a common indexes.conf file on the manager node.
2. Use the manager node to distribute the file across the set of peers.
These two steps are described below.
1. Edit indexes.conf
For details on configuring indexes.conf, read the topics in the chapters Manage indexes and Manage index storage in this manual. For a list of all indexes.conf attributes, see the indexes.conf specification file in the Admin Manual.
For the most part, you edit the cluster peer indexes.conf in the same way as for any indexer. However, there are a few differences to be aware of.
The indexes.conf repFactor attribute
When you add a new index stanza, you must set the repFactor attribute to "auto". This causes the index's data to be replicated to other peers in the cluster. For example:
[idx1]repFactor = autohomePath = $SPLUNK_DB/$_index_name/dbcoldPath = $SPLUNK_DB/$_index_name/colddbthawedPath = <path for thawed buckets>...
Note: By default, repFactor is set to 0, which means that the index will not be replicated. For clustered indexes, you must set it to "auto".
The only valid values for repFactor are 0 and "auto".
Resetting repFactor from "auto" to 0 will stop further replication, but it will not automatically remove copies of already replicated buckets. In addition, searches across buckets with multiple copies will return duplicate events. To free up associated disk space and eliminate the possibility of duplicate events, you must remove the excess copies manually.
Specify the index path attributes with forward-slash directory separators
In heterogeneous environments, it is possible that the manager node's operating system could use a different convention for specifying directory paths from the peer nodes' operating system. This presents a problem because you edit the indexes.conf file on the manager node but then you distribute it to the peers.
For example, if you have a Windows manager node and a set of Linux peers, the normal way to specify the homePath on the Windows manager node, where the file gets edited, would be to use the Windows backward-slash convention as a directory separator, while the Linux peers, where the file gets distributed, require forward slashes.
To deal with this possibility, the best practice is to always use forward slashes when specifying directory paths in in the index path attributes, no matter which operating systems your manager and peers use. For example:
homePath = $SPLUNK_DB/$_index_name/db
Splunk Enterprise always accepts the forward slash as a directory separator.
2. Distribute the new indexes.conf file to the peers
After you edit indexes.conf, you need to distribute it to the cluster's set of peer nodes. To learn how to distribute configuration files, including indexes.conf, across all the peers, read Update common peer configurations and apps.
For information about other types of peer configuration, including app distribution, read Peer node configuration overview.
View the indexes
To see the set of indexes on your peer nodes, click the Indexes tab on the manager node dashboard. See View the manager node dashboard.
Note: A new index appears under the tab only after it contains some data. In other words, if you configure a new index on the peer nodes, a row for that index appears only after you send data to that index.
