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!

Introduction to Splunk Observability Cloud - Building a Resilient Hybrid Cloud

Introduction to Splunk Observability Cloud - Building a Resilient Hybrid Cloud  In today’s fast-paced digital ...

Observability protocols to know about

Observability protocols define the specifications or formats for collecting, encoding, transporting, and ...

Take Your Breath Away with Splunk Risk-Based Alerting (RBA)

WATCH NOW!The Splunk Guide to Risk-Based Alerting is here to empower your SOC like never before. Join Haylee ...