Splunk® Enterprise

Distributed Search

Download manual as PDF

Download topic as PDF

Classic knowledge bundle replication

In classic knowledge bundle replication, the search head sends the knowledge bundle directly to each of its search peers. As such, classic replication uses the simplest mechanism for replicating the knowledge bundle, and it is appropriate for relatively small deployments.

For deployments with larger numbers of search peers, exceeding 15 or 20, the classic policy is not optimal, as it can result in slow bundle replication. For larger deployments, it is usually better to employ the cascading policy.

Configure classic bundle replication

Classic bundle replication is the default method for replicating the knowledge bundle. If you need to revert to this policy from some other policy, edit the replicationPolicy setting in the [replicationSettings] stanza of distsearch.conf on the search head:

[replicationSettings]
 
replicationPolicy = classic

You must restart the search head for the change to take effect.

The replicationThreads setting in distsearch.conf determines how many threads are available to the search head for sending bundles in parallel to search peers. Its default setting of "auto" usually provides the optimal thread allocation.

PREVIOUS
Modify the knowledge bundle
  NEXT
Cascading knowledge bundle replication

This documentation applies to the following versions of Splunk® Enterprise: 8.0.0


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

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