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!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...