Deployment Architecture

Restart activity

saeed
Explorer

All Splunk Apps are installed on Linux Servers and we will apply OS patch.

And i have 3 Indexers, 4 Search Heads, 1 Deployment Server and 1 Heavy Forwarder  (an Indexer Cluster is integrates with a SHC)

Could you please advise me what should i stop first or can i stop them at the same time? 

will i loss Data in this Activity?

Labels (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Yes, you can stop all instances of Splunk, but you will lose one of the main benefits of search head and indexer clustering.  It's better to stop one instance at a time.

Start with the DS then do the HF followed by the search heads.

I'd do the indexers last.  Be sure to go into maintenance mode when you start and take each off-line before patching.  Exit maintenance mode after patching all indexers.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Yes, you can stop all instances of Splunk, but you will lose one of the main benefits of search head and indexer clustering.  It's better to stop one instance at a time.

Start with the DS then do the HF followed by the search heads.

I'd do the indexers last.  Be sure to go into maintenance mode when you start and take each off-line before patching.  Exit maintenance mode after patching all indexers.

---
If this reply helps you, Karma would be appreciated.

saeed
Explorer

Thanks a lot

 
 

 

0 Karma
Get Updates on the Splunk Community!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...