Documentation > Splunk > Admin Manual > Set up data balancing

Admin Manual

 


How Splunk Works
Getting Started
Configuring a Splunk Deployment
Data Inputs
Hosts
Source Types
Timestamp Recognition
Events
Event Types
Meta Events
Fields
Segmentation
Saved Searches and Alerts
Authentication
Data Distribution
Granular Access Control
Distributed Search
Deployment Server
Index Management
Bundles
SplunkBase
Performance Tuning
Routine Maintenance
How-To
Troubleshooting
Reference

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

You can set up your forwarders 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 will send all events to the one that is still up, while simultaneously retrying the one that is down. If all servers are down, the forwarder will go into retry loops, and the queue will fill according to the queue configuration parameters.


Also, you can optionally specify back off and queue settings in outputs.conf. Please read about how to 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 will clone every event into 2 round-robin target groups.

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

This documentation applies to the following versions of Splunk: 3.0 , 3.0.1 , 3.0.2 , 3.1 , 3.1.1 , 3.1.2 , 3.1.3 , 3.1.4 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!