-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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: protect ruler remote-write overrides map with a mutex when creating new appenders #13676
Merged
cstyan
merged 1 commit into
grafana:main
from
verejoel:fix/ruler-appender-concurrent-access
Jul 30, 2024
Merged
fix: protect ruler remote-write overrides map with a mutex when creating new appenders #13676
cstyan
merged 1 commit into
grafana:main
from
verejoel:fix/ruler-appender-concurrent-access
Jul 30, 2024
Conversation
This file contains 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
verejoel
changed the title
Ruler: protect overrides map with a mutex when creating a new appender
fix: protect ruler remote-write overrides map with a mutex when creating new appenders
Jul 26, 2024
verejoel
force-pushed
the
fix/ruler-appender-concurrent-access
branch
from
July 26, 2024 10:38
000d1c4
to
55e0d9d
Compare
@cstyan pinging you for a review :) |
cstyan
approved these changes
Jul 30, 2024
@verejoel thanks! before I merge, can you confirm that you're just seeing this when you have many rules configured? it's not that you have few rules but multiple remote write endpoints for that ruler/tenant? |
Yes, we have around 800 rules configured. I was able to reduce the impact
by scaling to 10 replicas (so around 80 rules per replica). But still see a
crash about once every 30 minutes. The test case I wrote catches the
failure.
…On Mon, 29 Jul 2024 at 14:46, Callum Styan ***@***.***> wrote:
@verejoel <https://github.com/verejoel> thanks! before I merge, can you
confirm that you're just seeing this when you have many rules configured?
it's not that you have few rules but multiple remote write endpoints for
that ruler/tenant?
—
Reply to this email directly, view it on GitHub
<#13676 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALE5VOMOMVGJJNXQJ2TPQL3ZO3O6FAVCNFSM6AAAAABLQH6AKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGI2TIMJQGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@verejoel cool, thank you 👍 |
This was referenced Aug 15, 2024
This was referenced Oct 14, 2024
This was referenced Oct 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
This fixes an additional data race identified when creating new appenders in a ruler handling many hundreds of rules.
Which issue(s) this PR fixes:
Fixes #11569
Special notes for your reviewer: It's not possible to defer the unlock in the Appender function, as we access the registry later when update the tenant configuration. Therefore we just put the guard around the singular operation when we access the remote write config.
Checklist
CONTRIBUTING.md
guide (required)feat
PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.docs/sources/setup/upgrade/_index.md
production/helm/loki/Chart.yaml
and updateproduction/helm/loki/CHANGELOG.md
andproduction/helm/loki/README.md
. Example PRdeprecated-config.yaml
anddeleted-config.yaml
files respectively in thetools/deprecated-config-checker
directory. Example PR