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 (2)
0 Karma
Get Updates on the Splunk Community!

Fun with Regular Expression - multiples of nine

Fun with Regular Expression - multiples of nineThis challenge was first posted on Slack #regex channel ...

[Live Demo] Watch SOC transformation in action with the reimagined Splunk Enterprise ...

Overwhelmed SOC? Splunk ES Has Your Back Tool sprawl, alert fatigue, and endless context switching are making ...

What’s New & Next in Splunk SOAR

Security teams today are dealing with more alerts, more tools, and more pressure than ever.  Join us on ...