Deployment Architecture

How to update the search head configuration from the cluster master?

mciudad
Explorer

I'm trying to update the configuration of all the peers from my cluster master. With the indexers, it's eash to put the configuration file in $SPLUNK_HOME/etc/slave_apps/_cluster/local and then the indexer receives it, but I can't find any way to update the search head. Is there any similar (or not similar) way of doing it?

Thank you.

0 Karma
1 Solution

ppablo
Retired

Hi @mciudad

If you're trying to update configurations for search heads in a search head cluster, you should be using the Deployer instance to push changes. Check out this page from Splunk documentation covering how to configure the Deployer and how to push a configuration bundle to the search head cluster members.
http://docs.splunk.com/Documentation/Splunk/6.2.3/DistSearch/PropagateSHCconfigurationchanges

View solution in original post

ppablo
Retired

Hi @mciudad

If you're trying to update configurations for search heads in a search head cluster, you should be using the Deployer instance to push changes. Check out this page from Splunk documentation covering how to configure the Deployer and how to push a configuration bundle to the search head cluster members.
http://docs.splunk.com/Documentation/Splunk/6.2.3/DistSearch/PropagateSHCconfigurationchanges

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...

Index This | How many sevens are there between 1 and 100?

August 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...