-
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
roachtest: clearrange/checks=true failed: MVCCStats divergence #86542
Comments
n5 exited after it detected its MVCC Stats divergence.
cc @cockroachdb/replication |
Thanks @jbowens, I'll have a look. |
cc @cockroachdb/replication |
roachtest.clearrange/checks=true failed with artifacts on master @ 80c274877a917580af62be6eb0cd48c8c7ae9c08:
Parameters: |
This last failure seems a little different. The test timed out waiting for the last two merges to complete. |
The stats failure here is similar to what we saw over in #81429, where we also had a discrepancy in This all leads me to believe this may have been a pre-existing problem, some sort of race when writing system-local data. It's unclear to me if this would be owned by storage or KV, but I'd like to hand it over either way. |
cc: @itsbilal - reckon you could take a look? |
roachtest.clearrange/checks=true failed with artifacts on master @ 524fd14da3fefcd849f44a835cc5f88f5dbdadcc:
Parameters: |
I've yet to find a repro or come up with a reasonable cause for how we'd end up with stats delta in The failure from this morning seems to also be one about waiting for the last two merges to complete. That's more fixable - especially if it's a reliable-ish flake - but it is a separate issue entirely it seems. |
The stats divergence issue is likely resolved. The issue with the last two ranges failing to merge doesn't seem to reliably reproduce. Given this test hasn't failed in close to a month, I'm going to close it out. |
93837: backupccl: deflake TestClusterRestoreFailCleanup r=stevendanna a=msbutler This test occasionally flakes due to #86806. To prevent the flakiness, this patch manually sets the kv.bulkio.write_metadata_sst.enabled cluster setting to false. When #86806 gets addressed, this patch should be reverted. Epic: None Release note: None 93897: kvnemesis: ignore `SysBytes:10` MVCC stats discrepancy r=erikgrinaker a=erikgrinaker Resolves #93890. Touches #93896. Touches #93312. Touches #86542. Epic: none Release note: None Co-authored-by: Michael Butler <[email protected]> Co-authored-by: Erik Grinaker <[email protected]>
roachtest.clearrange/checks=true failed with artifacts on master @ aaf50e920ceff3c2863ab96b9e3614b8434b70a8:
Parameters:
ROACHTEST_cloud=gce
,ROACHTEST_cpu=16
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-18804
Epic CRDB-16237
The text was updated successfully, but these errors were encountered: