Choose the replication factor for the search head cluster
The replication factor determines the number of copies of each search artifact, or search result, that the cluster maintains. Replication occurs only for artifacts from scheduled saved searches. The cluster does not replicate results from ad hoc searches or realtime searches.
Effect of the replication factor
The cluster can tolerate a failure of (replication factor - 1) members without losing any search artifacts. For example, to ensure that your system can handle the failure of two members without losing search artifacts, configure a replication factor of 3. This configuration directs the cluster to store three copies of each search artifact, with each copy on a different member. If two members go down, the artifact is still available on a third member.
The default value for the replication factor is 3. This number is sufficient for most purposes.
Even with a large cluster of, for example, 50 search heads, you do not need a commensurately large replication factor. As long as you do not lose the replication factor number of members, at least one copy of each search artifact still exists somewhere on the cluster and is accessible to all cluster members. Any search head in the cluster can access any search artifact by proxying from a search head storing a copy of that artifact. The proxying operation is fast and unlikely to impede access to search results from any search head.
Note: The replication factor determines only the number of copies of search artifacts that the cluster maintains. It does not affect the replication of runtime configuration changes, such as new saved searches. Those changes get replicated to all cluster members by a different process. If you have 50 search heads, each of those 50 gets a copy of such configuration changes. See Configuration updates that the cluster replicates.
Replication factor configuration
All cluster members must use the same replication factor. The
server.conf attribute that determines the replication factor is
You specify the replication factor during deployment of the cluster, as part of member initialization. See Initialize cluster members.
You can change the replication factor post-deployment, if necessary, but it is recommended that you consult Splunk Support before doing so. If you change the replication factor on one member, you must change it on all members. For information on modifying configuration values, see Configure the search head cluster.
For more information
For information on how the cluster replicates search artifacts, see How the cluster handles search artifacts. That subtopic describes several key points about artifact replication, among them:
- In some cases, the cluster might replicate more than the replication factor number of a search artifact.
- Artifact proxying, along with additional replication, occurs if a member without a copy of the artifact needs access to it.
- If a member goes down, the cluster replaces the artifact copies that were being stored on that member.
See List search artifacts to learn how to view the set of artifacts in the cluster and on individual members.
Configure the search head cluster
Set a security key for the search head cluster
This documentation applies to the following versions of Splunk® Enterprise: 6.2.0, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.2.12, 6.2.13, 6.2.14, 6.2.15, 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11, 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 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.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.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.3.0