-
Notifications
You must be signed in to change notification settings - Fork 15.2k
Add TTL-enabled LRU cache for StatsD metrics aggregation #51792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Add TTL-enabled LRU cache for StatsD metrics aggregation #51792
Conversation
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
|
Some static checks fail.... though I am not an statsd expert... @AutomationDev85 Do you have an opinion to the configs? |
…/shubham36deshpande/airflow into issue-50645-statsd-ttl-lru-cache
{{- else}} | ||
args: | ||
- "--statsd.mapping-config=/etc/statsd-exporter/mappings.yml" | ||
- "--statsd.cache-size={{ .Values.statsd.cacheSize }}" | ||
- "--statsd.cache-type={{ .Values.statsd.cacheType }}" | ||
- "--ttl={{ .Values.statsd.ttl }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On my second pass-review. If .Values.statsd.args
is defined this basically means the cacheSize
/cacheType
and ttl
parameters are ignored.
Can you at least add this to the docs or is there a way to append the parameters to the args as well (merge them)?
…Helm chart
This PR introduces a TTL (time-to-live) mechanism in conjunction with an LRU (least-recently-used) cache for StatsD metric aggregation. The change is designed to automatically clean up stale or unused metric entries, preventing uncontrolled memory growth in long-running statsd daemons—a problem highlighted in issue #50645.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in airflow-core/newsfragments.