-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
kv/kvserver: TestTenantRateLimiter failed #101901
Comments
Looks like a legit race. Conservatively marking as GA blocker.
|
This was a result of the change to the histograms. @kvoli and @coolcom200 can you take a quick look at this. It seems like we just need a read lock in |
You're right, we aren't locking when accessing the I'll post a patch to resolve and backport. |
It makes sense to also lock it in |
I don't think we are able to lock in
|
It was possible for concurrent `Update` and `ToPrometheusMetric` calls to race due to a read lock not being held when calling `ToPrometheusMetric`. This patch adds such a lock and updates the structure to conform to the regular convention of a `mu` struct field, which indicates fields requiring a lock. Fixes: cockroachdb#101901 Release note: None
101949: metric: fix race in manual histogram r=andrewbaptist a=kvoli It was possible for concurrent `Update` and `ToPrometheusMetric` calls to race due to a read lock not being held when calling `ToPrometheusMetric`. This patch adds such a lock and updates the structure to conform to the regular convention of a `mu` struct field, which indicates fields requiring a lock. ``` dev test pkg/kv/kvserver -f TestTenantRateLimiter -v --stress --race ... 288 runs so far, 0 failures, over 14m15s ``` Fixes: #101901 Release note: None Co-authored-by: Austen McClernon <[email protected]>
It was possible for concurrent `Update` and `ToPrometheusMetric` calls to race due to a read lock not being held when calling `ToPrometheusMetric`. This patch adds such a lock and updates the structure to conform to the regular convention of a `mu` struct field, which indicates fields requiring a lock. Fixes: #101901 Release note: None
Resolved when backports merged. |
Manual reconstruction of cockroachdb#101949. It was possible for concurrent `Update` and `ToPrometheusMetric` calls to race due to a read lock not being held when calling `ToPrometheusMetric`. This patch adds such a lock. Fixes: cockroachdb#101901 Release note: None
Closed on #102009 |
kv/kvserver.TestTenantRateLimiter failed with artifacts on release-23.1 @ ad6ce866ea3b5c5bb47ba9a0ac19b721a0c98add:
Parameters:
TAGS=bazel,gss,race
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-27180
The text was updated successfully, but these errors were encountered: