Installation

Does kvstore upgrade from 8.0 to 8.2 needs to be done on the cluster master?

ggvaca
Explorer

Hello,

I am upgrading our splunk instance from 8.0 to 8.2. I noticed after following the kvstore upgrade which followed the upgrade to 8.2, which I did on our cluster heads, and they all have WiredTiger on them now. 

ggvaca_0-1656014421957.png

Logging into our cluster master, I get an error saying I need to upgrade the kvstore. This comes up like 30+ minutes after the upgrade. I look at the cluster master and run the same command for the kvstore status, and it says that it has the old kvstore on it still.

ggvaca_1-1656014531361.png
Am I supposed to be going onto each box and upgrading the kvstore on them? The instructions said the search heads and so that's what I followed. 

 

Labels (2)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

You don't need to upgrade the KVStore on all instances.  Indexers, for example, do not use KVStore.  The CM, however, might so it makes sense to upgrade it there.  You'll likely also need to upgrade it on your MC node.

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

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

You don't need to upgrade the KVStore on all instances.  Indexers, for example, do not use KVStore.  The CM, however, might so it makes sense to upgrade it there.  You'll likely also need to upgrade it on your MC node.

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

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

What are Community Office Hours?Community Office Hours is an interactive 60-minute Zoom series where ...

Updated Data Type Articles, Anniversary Celebrations, and More on Splunk Lantern

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

A Prelude to .conf25: Your Guide to Splunk University

Heading to Boston this September for .conf25? Get a jumpstart by arriving a few days early for Splunk ...