Skip to content
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

fix: do not cleanup timeseries which are used in multiple remote write contexts #6206

Merged
merged 5 commits into from May 6, 2024

Conversation

AndrewChubatiuk
Copy link
Contributor

@AndrewChubatiuk AndrewChubatiuk commented Apr 29, 2024

When at least one remote write has deduplication configured it cleans up timeseries while they can be in use by another remote write without deduplication

Fixes #6205

Describe Your Changes

Please provide a brief description of the changes you made. Be as specific as possible to help others understand the purpose and impact of your modifications.

Checklist

The following checks are mandatory:

Copy link
Collaborator

@hagen1778 hagen1778 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the quick fix!
I'd like to propose additional changes to this PR:

  1. Add comment to func (rwctx *remoteWriteCtx) TryPush that it shouldn't modify tss slice
  2. Add tests which would help to verify vmagent panic on remoteWrite.streamAggr.dedupInterval #6205 vmagent: wrong relabeling via -remoteWrite.urlRelabelConfig #599 and vmagent lost some metrics  #467 won't repeat anymore
  3. Add changelog with bugfix description and affected versions

AndrewChubatiuk and others added 5 commits May 6, 2024 11:29
Signed-off-by: hagen1778 <roman@victoriametrics.com>
* fix the error message comparing in and out series
* revert making `newAggregatorsFromData` public, as this introduces unrelated
changes. Using `LoadFromFile` instead.

Signed-off-by: hagen1778 <roman@victoriametrics.com>
@hagen1778 hagen1778 force-pushed the do-not-cleanup-ts-in-dedup branch from 2d384ec to be4d8f4 Compare May 6, 2024 09:29
Copy link
Collaborator

@hagen1778 hagen1778 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

Please see minor updates below:
f1fecc9
be4d8f4

@hagen1778 hagen1778 merged commit 8797718 into master May 6, 2024
8 checks passed
@hagen1778 hagen1778 deleted the do-not-cleanup-ts-in-dedup branch May 6, 2024 10:09
hagen1778 pushed a commit that referenced this pull request May 6, 2024
…multiple remote write contexts (#6206)

When at least one remote write has deduplication configured it cleans up
timeseries while they can be in use by another remote write without
deduplication

#6205
---------

Signed-off-by: hagen1778 <roman@victoriametrics.com>
Co-authored-by: hagen1778 <roman@victoriametrics.com>
(cherry picked from commit 8797718)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

vmagent panic on remoteWrite.streamAggr.dedupInterval
2 participants