Related Answers
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 bundle (>200MB), bundle validation might fail due to various timeouts. To remediate:
1. Edit the master's server.conf file to include these settings:
[sslConfig] allowSslCompression = false [clustering] heartbeat_timeout = 600
2. Restart the master.
3. Push a bundle that includes some updated server.conf settings to the peers:
a. Move to a temporary location any apps that you added to the bundle since the last successful push.
b. Create $SPLUNK_HOME/etc/master-apps/_cluster/local/server.conf on the master with these settings:
[general] useHTTPClientCompression = true [clustering] heartbeat_period = 30 cxn_timeout = 300 send_timeout = 300 rcv_timeout = 300
c. Push the bundle to the peers:
splunk apply cluster-bundle
This will initiate a rolling restart of all peers.
4. Re-add into the bundle the apps that you deleted from the bundle in step 3a, leaving the new server.conf file there as well.
5. Push the expanded bundle to the peers.
|
PREVIOUS Anomalous bucket issues |
NEXT About archiving indexes with Hadoop Data Roll |
This documentation applies to the following versions of Splunk® Enterprise: 6.2.0, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.2.12, 6.2.13, 6.2.14, 6.2.15, 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.3.14, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11, 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10
Feedback submitted, thanks!