Getting Data In

Poor indexing rate in indexer

mwong
Splunk Employee
Splunk Employee

In SoS app, it is found that the indexing rate is limited to about 200Kb/s.

Tags (1)
0 Karma

mwong
Splunk Employee
Splunk Employee

Sometimes a forwarder app is accidentally deployed to an indexer. It is normally limited by the throughput of network bandwidth.

[thruput]
maxKBps = 256

Please try to use the command ./splunk cmd btool limits list thruput to check if the maxKBps is set to 0. Otherwise indexing rate of an indexer will be limited and not fully utilized the IO rate of the disk system.

You may also refer the link below showing that index_thruput is controlled by thruput value.
http://wiki.splunk.com/Community:HowIndexingWorks

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 ...