Splunk® Enterprise

Managing Indexers and Clusters of Indexers

Download manual as PDF

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

Configuration bundle issues

This topic describes problems that can arise when pushing a configuration bundle from the master to the peer nodes.

Bundle validation failure when pushing a very large bundle

If you attempt to push a very large configuration bundle (>200MB), bundle validation might fail due to various timeouts. To remediate, you can adjust the number of peers that the master simultaneously pushes the bundle to.

By default, the master pushes the bundle to all peers simultaneously. The max_peers_to_download_bundle setting in server.conf provides a means to limit the number of peers that receive the bundle simultaneously.

For example if you set max_peers_to_download_bundle = 3, the master pushes the bundle to three peers at a time. When one peer finishes the download, the master pushes the bundle to another peer, and so on, until all peers have received the bundle.

For details, see the server.conf specification.

PREVIOUS
Anomalous bucket issues
  NEXT
About archiving indexes with Hadoop Data Roll

This documentation applies to the following versions of Splunk® Enterprise: 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

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

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters