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!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...