fix(aggregate transform): Fix memory leaks with high-cardinality metrics#24357
Closed
thomasqueirozb wants to merge 1 commit into
Closed
fix(aggregate transform): Fix memory leaks with high-cardinality metrics#24357thomasqueirozb wants to merge 1 commit into
thomasqueirozb wants to merge 1 commit into
Conversation
|
This is a bugfix, please integrate |
Contributor
|
This would also fix: #24589 |
This was referenced Mar 17, 2026
Contributor
Author
|
Superseded by #24943. However memory leak is still an issue on diff and maybe mean, stdev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes two memory leaks in the aggregate transform that caused unbounded memory growth with high-cardinality metrics. The first eliminated an unnecessary HashMap clone on every flush. The second prevented prev_map from accumulating stale metric series indefinitely.
Vector configuration
How did you test this PR?
Created a Python script to generate high-cardinality changing metrics (500 unique series per batch, constantly changing to simulate pod churn). Ran both the old and fixed versions with Diff aggregation mode for 10 minutes each, monitoring memory usage every 10 seconds.
Metric generator script (metric_generator.py)
Test script (test_10min.sh)
Results:
All 14 existing aggregate transform unit tests pass.
Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References