Deployment Architecture

How does a Search Head Cluster determine if a restart is necessary when a configuration bundle is applied?

muebel
SplunkTrust
SplunkTrust

A configuration bundle can be applied to a Search Head Cluster (SHC) from a Deployer with the command:

splunk apply shcluster-bundle

The documentation indicates that the cluster somehow determines if a rolling restart is necessary as part of the bundle application

Each cluster member applies the app tarballs locally. If a rolling restart is determined necessary, approximately 10% of the members then restart at a time, until all have restarted.

http://docs.splunk.com/Documentation/Splunk/6.5.2/DistSearch/PropagateSHCconfigurationchanges

How does the cluster determine if a rolling restart is necessary? I'm working with custom javascript/css, and have found that a rolling restart doesn't occur when pushing out new files, or new versions of the files.

0 Karma
1 Solution

somesoni2
Revered Legend

From the same page, (search for keyword 'app.conf'),

For information on which configuration changes trigger restart, see $SPLUNK_HOME/etc/system/default/app.conf. It lists the configuration files that do not trigger restart when changed. All other configuration changes trigger restart.

View solution in original post

somesoni2
Revered Legend

From the same page, (search for keyword 'app.conf'),

For information on which configuration changes trigger restart, see $SPLUNK_HOME/etc/system/default/app.conf. It lists the configuration files that do not trigger restart when changed. All other configuration changes trigger restart.

View solution in original post

muebel
SplunkTrust
SplunkTrust

awesome. ty

0 Karma
.conf21 CFS Extended through 5/20!

Don't miss your chance
to share your Splunk
wisdom in-person or
virtually at .conf21!

Call for Speakers has
been extended through
Thursday, 5/20!