-
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: TestFlowControlRaftMembership failed #125736
Comments
This seems to be a side-effect of the changes here: #125613. Specifically coming from As storage on-call, I can take this one. |
We saw this before too and it was fixed: cockroachdb/pebble#3555. Unable to reproduce the non-monotonicity inside pebble using |
Seems like we are doing a flushable ingest at the time of this failure:
|
125571: roachtest: grafana annotations read creds from cloud storage r=herkolategan,renatolabs a=DarrylWong As of #124099 we now store the service account creds in cloud storage. We already use this to access prometheus when generating dynamic configs. This change does the same for Grafana annotations by extracting the common logic into a helper. This will allow users to have access to Grafana annotations out of the box locally, and limit the amount of benign but potentially confusing warnings about invalid credentials. Release note: none Fixes: none Epic: none 126084: jobs: limit number of retained dsp-diag-url info rows r=dt a=dt Fixes #126083. 126109: kvserver: deflake `WALBytesWritten` metric r=raduberinde a=aadityasondhi There is a race condition in Pebble metrics where sometimes the WAL is rotated prior to updated the BytesIn metric to account for the previous WAL. The metrics collection call happens async so it can sometimes cause this metric to decrease for a scrape window. Fixes: #125736. Release note: None 126114: sql: avoid slow lock verification in TestSchemaChangeAfterCreateInTxn r=rafiss a=rafiss The addition of test-only verification pushed this test over the timeout sometimes, such that running it under the deadlock detector would cause spurious failures. We avoid this by making the test smaller under deadlock, like we do for race builds. fixes #126075 Release justification: test only change Release note: None Co-authored-by: DarrylWong <[email protected]> Co-authored-by: David Taylor <[email protected]> Co-authored-by: Aaditya Sondhi <[email protected]> Co-authored-by: Rafi Shamim <[email protected]>
There is a race condition in Pebble metrics where sometimes the WAL is rotated prior to updated the BytesIn metric to account for the previous WAL. The metrics collection call happens async so it can sometimes cause this metric to decrease for a scrape window. Fixes: cockroachdb#125736. Release note: None
kv/kvserver.TestFlowControlRaftMembership failed on master @ 3aa5bdf40527e2f60b179094403b4302a1c2cbe1:
Fatal error:
Stack:
Log preceding fatal error
Parameters:
attempt=1
race=true
run=1
shard=3
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-39580
The text was updated successfully, but these errors were encountered: