Documentation > Splunk > Admin Manual > Set up data balancing

Admin Manual

 


How Splunk Works
Getting Started
Data Inputs
Data Distribution
Indexing
Timestamps
Fields
Hosts
Source Types
Event Types
Transaction Types
Search
Distributed Search
Security
Data Management
Deployment Server
Performance Tuning
Configuration Files
Applications
Reference
Troubleshooting

Set up data balancing

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

Contents

Set up data balancing

Set up your forwarding servers to balance outputs by sending events in a round-robin fashion to separate Splunk servers. To set up data balancing, add a stanza to outputs.conf.


Configuration

Edit $SPLUNK_HOME/etc/bundles/local/outputs.conf: 


[tcpout:FooGroup]
server=$IP:$PORT, $IP2:$PORT2, etc...

Specify the $IP:$PORT of the Splunk servers that will receive the forwarded data. You can enter any number of servers for Splunk to round-robin between. If one of the receiving servers goes down, the forwarder sends all events to the one that is still up, while simultaneously retrying the one that is down. If all servers are down, the forwarder goes into retry loops, and the queue fills according to the queue configuration parameters.


Also, you can optionally specify back off and queue settings in outputs.conf. For more information, read Configure outputs.conf.


Example 

[tcpout:SwanGroup]
server=10.1.1.197:9997, 10.1.1.200:9999
[tcpout:PearlGroup]
server=10.1.1.220:9997, 10.1.1.300:9999

With this configuration, Splunk clones every event into 2 round-robin target groups.

Retrieved from "http://docs.splunk.com/Documentation/Splunk/3.2.6/Admin/SetUpDataBalancing"

This documentation applies to the following versions of Splunk: 3.2 , 3.2.1 , 3.2.2 , 3.2.3 , 3.2.4 , 3.2.5 , 3.2.6 View the Article History for its revisions.


You must be logged into splunk.com in order to post comments. Log in now.

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.

Feedback submitted, thanks!