Splunk Enterprise

Higher memory usage with 9.4.0 splunkd process.

hrawat
Splunk Employee
Splunk Employee

Apart from https://community.splunk.com/t5/Splunk-Enterprise/Linear-memory-growth-with-Splunk-9-4-0-and-above/m...
Some splunk instances(UF/HF/SH/IDX) might see higher memory usage after the upgrade.

hrawat_0-1740696908616.png

9.4.0 has introduced new active channel cache. It has a cache TTL of 3600 sec.

active_eligibility_age = <integer>
* The time, in seconds, after which splunkd removes an idle input
  channel from the active channel cache to free up memory.
* Default: 3600



Before 9.4.0, splunkd was using inactive channel cache. It had a cache ttl of 330 sec. It's not used anymore.

inactive_eligibility_age_seconds = <integer>
* Time, in seconds, after which an inactive input channel will be removed from
  the cache to free up memory.
* Default: 330



Because of high active channel cache TTL, splunkd memory footprint might be higher on some splunk deployments.

In limits.conf reduce active channel cache TTL to 330 ( 9.4.2 onwards, by default it's 330)

 

 

[input_channels]
active_eligibility_age = 330

 

 

 

 

Labels (1)
Tags (1)
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...