Deployment Architecture

Best practice for Shutting entire Splunk Distributed Environmen.

sarwshai
Communicator

Got Cluster Master, Indexers, Deployment Server, Heavy Forwarder, Deployment Server, Search Heads, Universal Forwarders.
In what sequence should i decommission the servers so as to shutdown the whole environment smoothly?

0 Karma

broberg
Communicator

Hi.
If you want to avoid alot of error messages, or if you are migrating.
I would start with UFs and HF data.

Then Cluster in maintane mode followed by shutting down indexers, Cluster master,.
Then in the end search heads and deploymentservers (even if you can start with them aswell)

When starting up the environment, do it in reverse. Cluster master, indexer, searchhead, deploymentserver and start to onboard data.

Get Updates on the Splunk Community!

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!

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

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...