Getting Data In

Does a change to props.conf require an indexer rolling restart?

Ultra Champion

I'm about to implement the change in Why isn't the timestamp being recognized ?

It will be in $SPLUNK_HOME/etc/system/local/props.conf.

Does it require an indexer rolling restart?

0 Karma
1 Solution

SplunkTrust
SplunkTrust

Depends. Nice answer, huh?

If you put it in $SPLUNK_HOME/etc/system/local/props.conf, then it will not be controlled by the cluster master, and will require a rolling restart. And you will have to do it on each indexer manually.

If you put it in the right place (which is not $SPLUNK_HOME/etc/system/local/props.conf), then you can just deploy the changes from the CM by putting it in the master-apps directory structure for the sourcetype you want. Then the rolling restart is not required, because it will be handled by the CM.

Is there a compelling reason you want to put it in system/local?

View solution in original post

0 Karma

SplunkTrust
SplunkTrust

Depends. Nice answer, huh?

If you put it in $SPLUNK_HOME/etc/system/local/props.conf, then it will not be controlled by the cluster master, and will require a rolling restart. And you will have to do it on each indexer manually.

If you put it in the right place (which is not $SPLUNK_HOME/etc/system/local/props.conf), then you can just deploy the changes from the CM by putting it in the master-apps directory structure for the sourcetype you want. Then the rolling restart is not required, because it will be handled by the CM.

Is there a compelling reason you want to put it in system/local?

View solution in original post

0 Karma

Ultra Champion

It's interesting, for the search heads we have specific apps but not for the indexers...

0 Karma

Ultra Champion

Much appreciated @cpetterborg

0 Karma
State of Splunk Careers

Access the Splunk Careers Report to see real data that shows how Splunk mastery increases your value and job satisfaction.

Find out what your skills are worth!