Deployment Architecture

Restart order/procedure after updating server.conf with new master_uri & pass4SymmKey

richardgosnay
Explorer

Hi Guys,

I have:

1 x Search Node
1 x Master Node
 - 2 x Peer Nodes
1 x Deployment Node

I've updated the master_uri & pass4SymmKey in the Search node and restarted it Splunk via the GUI, this worked fine and the license page is showing the new values.  However, I am a bit reluctant to just change/restart the other nodes for fear of any bucket/replication issues.

Am I ok to update the Master Node the same and perform a normal restart? Then update the Peer Nodes and perform a Rolling Restart?

If not, what it is the best way to apply the conf changes and apply them? I did try searching the documentation but I got a bit lost.

Thank you in advance.

Labels (3)
0 Karma
Get Updates on the Splunk Community!

Splunk Forwarders and Forced Time Based Load Balancing

Splunk customers use universal forwarders to collect and send data to Splunk. A universal forwarder can send ...

NEW! Log Views in Splunk Observability Dashboards Gives Context From a Single Page

Today, Splunk Observability releases log views, a new feature for users to add their logs data from Splunk Log ...

Last Chance to Submit Your Paper For BSides Splunk - Deadline is August 12th!

Hello everyone! Don't wait to submit - The deadline is August 12th! We have truly missed the community so ...