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
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!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...