Installation

Update out of order

vaylor
Engager

Our Splunk environment is deployed over 5 servers: 1 cluster master, 1 deployment server, 2 indexers, and 1 KV store / search head. We are also using an automated patch management system that managed to push the update to 8.0 to 2 of these servers: the deployment server and the search head. This means that our cluster master and our indexers are still on 7.3.2.

What's the best way to get everything to 8.0 without causing any damage?

Labels (3)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

The steps for upgrading an indexer cluster are documented at https://docs.splunk.com/Documentation/Splunk/8.0.0/Indexer/Upgradeacluster

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

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

The steps for upgrading an indexer cluster are documented at https://docs.splunk.com/Documentation/Splunk/8.0.0/Indexer/Upgradeacluster

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

richgalloway
SplunkTrust
SplunkTrust

IMO, 8.0 is not a patch. It's a major version change that should have been tested in dev/QA before it was deployed to production. Your automated patch system is broken.

Why do you have a deployer if you don't have a search head cluster?

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...