Monitoring Splunk

How do I fix KVStore error in indexer cluster

emallinger
Communicator

Hello,

I used :

|rest /services/server/info|table host kvStoreStatus

to check kvstore status after upgrading splunk from 8.0.4.1 to 8.1.3.

Results are coherent with messages for SHC. It's taken care of.

 

But for my indexers (in a cluster), the value is either "ready" or "failed".

I'm not sure I understand what either really mean. And no clue as how to fix it, as my understanding is that the usual command for that are for search-heads.

Does this mean I can apply the same procedure as :

https://docs.splunk.com/Documentation/Splunk/8.2.1/Admin/ResyncKVstore

Thanks

Regards,

Ema

Labels (1)
Tags (1)
0 Karma
1 Solution

venkatasri
SplunkTrust
SplunkTrust

Hi @emallinger 

There is a lot to explain, why don't you look at already answered query here - https://community.splunk.com/t5/Getting-Data-In/Where-should-the-kvstore-be-deployed-in-a-distribute...

---

An upvote would be appreciated if this reply helps!

View solution in original post

emallinger
Communicator

Hello,

Thanks , that was exactly what I was looking for !

It pertains to what I understood but wasn't sure enough of.

Regards,

Ema

0 Karma

venkatasri
SplunkTrust
SplunkTrust

Hi @emallinger 

There is a lot to explain, why don't you look at already answered query here - https://community.splunk.com/t5/Getting-Data-In/Where-should-the-kvstore-be-deployed-in-a-distribute...

---

An upvote would be appreciated if this reply helps!

Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

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

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...