Getting Data In

Forwarder Load Balancer duplicating data problem.

clyde772
Communicator

I am trying to have LB setup to send large volume of data into 4 different INDEXES in round robin structure.

But when I set up the forwarder LB, the forwarder sends exact duplicate copies of data into 4 of those indexers instead of scattering the data amongst the indexers.

So 100G sent from forwarder, 100G shows up on each indexers, instead of 25G per indexers. How can I setup forwarder to load 100G of data into 4 indexer consuming 25G on each indexers.

Here is my outputs.conf following the docementation. Am I missing any tricks?

================ outputs.conf =====================

[tcpout:10.150.206.29_9997]
disabled=false
autoLB = true
autoLBFrequency=40
server = 10.150.206.29:9997

[tcpout:10.150.233.4_9997]
disabled=false
autoLB = true
autoLBFrequency=40
server = 10.150.233.4:9997

[tcpout:10.154.39.173_9997]
disabled=false
autoLB = true
autoLBFrequency=40
server = 10.154.39.173:9997

[tcpout:10.150.201.29_9997]
disabled=false
autoLB = true
autoLBFrequency=40
server = 10.150.201.29:9997

[tcpout]
defaultGroup = 10.150.206.29_9997,10.150.233.4_9997,10.154.39.173_9997,10.150.201.29_9997

=====================================================

Tags (2)
0 Karma

lguinn2
Legend

I think of it this way: each stanza sets up a duplicate output stream. So what you need is:

[tcpout]
defaultGroup = my_indexers

[tcpout:my_indexers]
disabled=false
autoLB = true
autoLBFrequency=40
server = 10.150.206.29:9997,10.150.233.4:9997,10.154.39.173:9997,10.150.201.29:9997

And it's shorter, too!

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