Deployment server and search head pooling
With search head pooling, all search heads access a single set of configurations, so you don't need to use a deployment server or a third party deployment management tool like Puppet to push updates to multiple search heads. However, you might still want to use a deployment tool with search head pooling, in order to consolidate configuration operations across all Splunk Enterprise instances.
If you want to use the deployment server to manage your search head configuration, note the following:
1. Designate one of the search heads as a deployment client by creating a
deploymentclient.conf file in
$SPLUNK_HOME/etc/system/local and specifying its deployment server. You only need to designate one search head as a deployment client.
deploymentclient.conf, set the
repositoryLocation attribute to the search head's shared storage mountpoint. You must also set
serverRepositoryLocationPolicy=rejectAlways, so that the locally set
repositoryLocation gets used as the download location.
serverclass.conf on the deployment server, define a server class for the search head client.
For detailed information on the deployment server, see "About deployment server" in the Updating Splunk Enterprise Instances manual.
Manage configuration changes
Select timing for configuration refresh
This documentation applies to the following versions of Splunk® Enterprise: 6.5.7, 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.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9
Feedback submitted, thanks!