Getting Data In

Universal Forwarder to different index server ports

fuster_j
Path Finder

Hi,

Is there any advantage to setup up Universal Forwarder to communicate different ports with index servers with load balancing instead all go to port 9997?

[tcpout]

autoLB = true

autoLBFrequency = 10

compressed = false

defaultGroup = AA

[tcpout:AA]

server = a1-abc.com:9995,b1.abc.com:9996,c1.abc.com:9997

Tags (1)
0 Karma

fuster_j
Path Finder

I'm think that each TCP session will have its own send/receive buffers. My real question is will they communicate concurrently in the load balancing mode?

0 Karma

Ayn
Legend

None at all that I can think of. Did you have an idea yourself, since you asked?

0 Karma
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!

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...