Splunk Enterprise

KVStore Memory Leak- How to manage without restarting every week?

andrew_burnett
Path Finder

Our KVStore, which is wiredTiger, slowly grows and consumes the entire cache and then will eventually grow outside the cache until restarted. It requires rolling restarts about once a week, and has persisted for months. Anyone else had this issue?

Labels (1)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

It might be completely unrelated to your case but I had an issue when kvstore was configured as wiredTiger but the database files themselves hadn't been migrated yet.

The kvstore would refuse to start but splunkd would start leaking memory like crazy to the point of oomkiller.

0 Karma

andrew_burnett
Path Finder

Unfortunately kvstore is running and starting normally

0 Karma
Get Updates on the Splunk Community!

Wrapping Up Cybersecurity Awareness Month

October might be wrapping up, but for Splunk Education, cybersecurity awareness never goes out of season. ...

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...

What's New in Splunk Observability - October 2025

What’s New?    We’re excited to announce the latest enhancements to Splunk Observability Cloud and share ...