Deployment Architecture

index delays with universal forwarder's parsing and tcpout queue full

cwl
Contributor

We are using 5.0.3 universal forwarder to send data to our 5.0.3 cluster environment.

We have enabled useACK because it is recommended as mentioned in splunk's documentation when using cluster but after enabling useACK we are seeing's our universal forwarder's parsing queue and tcpout queue quite full and data is getting indexed with delays.

We have already set thruput value in limits.conf to "maxKBps = 0" and we have checked with our network administrator that we don't have any network issues.

Our indexers seem to be working fine without any full queues. How can I fix this issue ?

1 Solution

cwl
Contributor

When you enable useACK, you have to increase your forwarder's maxQueueSize to 7MB in outputs.conf to ensure your forwarder does not get blocked while waiting for acknowledgment from an indexer.

[tcpout] 
maxQueueSize = 7MB

Please refer below documentation for details and note that this is adjusted automatically in 5.0.4 and beyond.
link:Configure the wait queue size

View solution in original post

cwl
Contributor

When you enable useACK, you have to increase your forwarder's maxQueueSize to 7MB in outputs.conf to ensure your forwarder does not get blocked while waiting for acknowledgment from an indexer.

[tcpout] 
maxQueueSize = 7MB

Please refer below documentation for details and note that this is adjusted automatically in 5.0.4 and beyond.
link:Configure the wait queue size

dfrankekcg
Explorer

Per http://docs.splunk.com/Documentation/Splunk/6.1.1/Forwarding/Protectagainstlossofin-flightdata, maxQueueSize=auto is recommended for forwarder version 5.04 and above.

0 Karma
Get Updates on the Splunk Community!

Aligning Observability Costs with Business Value: Practical Strategies

 Join us for an engaging Tech Talk on Aligning Observability Costs with Business Value: Practical ...

Mastering Data Pipelines: Unlocking Value with Splunk

 In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...