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.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...