Deployment Architecture

distsearch.conf replicationThreads

sfmandmdev
Path Finder

What factors should be taken into consideration in deciding the appropriate number of replicationThreads? Are there any performance considerations for increasing this value?

1 Solution

Ledion_Bitincka
Splunk Employee
Splunk Employee

The default number of replication threads is set to 5 by default. You should take into consideration the number of search peers, the network bandwidth between search head and peers as well as the size of the bundles when changing this value. Consider increasing it if you have a lot of peers, the link between SH and peers is slow and the bundle are large. If you have SSL enabled between SH and peers you will incur a high cpu load during the transfer because the bundle will be encrypted, compressed and sent to the peers by X thread in parallel.

View solution in original post

Ledion_Bitincka
Splunk Employee
Splunk Employee

The default number of replication threads is set to 5 by default. You should take into consideration the number of search peers, the network bandwidth between search head and peers as well as the size of the bundles when changing this value. Consider increasing it if you have a lot of peers, the link between SH and peers is slow and the bundle are large. If you have SSL enabled between SH and peers you will incur a high cpu load during the transfer because the bundle will be encrypted, compressed and sent to the peers by X thread in parallel.

Get Updates on the Splunk Community!

What's New in Splunk Enterprise 9.4: Features to Power Your Digital Resilience

Hey Splunky People! We are excited to share the latest updates in Splunk Enterprise 9.4. In this release we ...

Take Your Breath Away with Splunk Risk-Based Alerting (RBA)

WATCH NOW!The Splunk Guide to Risk-Based Alerting is here to empower your SOC like never before. Join Haylee ...

SignalFlow: What? Why? How?

What is SignalFlow? Splunk Observability Cloud’s analytics engine, SignalFlow, opens up a world of in-depth ...