Deployment Architecture

What does this mean? ERROR IntrospectionGenerator:resource_usage - KVStorageProvider - Internal read failed with error code '13436' and message 'not master or secondary; cannot currently read from this replSet member'

jgoddard
Path Finder

I have been having issues with the KV Store under 6.2.0 and 6.2.1, mostly in my search head cluster. The first issue I have is that the KV store doesn't always get stopped by a splunk restart, resulting in the mongod process being left running and the KV port bound. This prevents splunk from restarting, which has resulted in a couple of cluster failures/issues. I see an existing unanswered question about this one (http://answers.splunk.com/answers/191451/splunk-62-mongod-does-not-seem-t).

The error in the subject line i am only seeing on one of three search head cluster members. Has anyone seen this before and even better, what do I do to resolve it?

amirofmn
Explorer

Curious if a solution was ever found for this particular error message.

0 Karma

bpaul_splunk
Splunk Employee
Splunk Employee

One way this message can be displayed is if the number of search head cluster members is greater than the KVStore instances. Please check to make sure KVStore is enabled on all the search head cluster members.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...