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.
Bundle validation remains in progress and does not complete
If the bundle validation process remains in progress on the master, and no validation response appears, you must cancel and reset the the bundle push operation to escape the in-progress state.
To cancel and reset the bundle push operation, hit the following endpoint on the master: cluster/master/control/default/cancel_bundle_push.
Anomalous bucket issues
About archiving indexes with Hadoop Data Roll
This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 8.0.0, 8.0.1, 8.0.2