-
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: c2c/weekly/kv50 failed #112823
Comments
roachtest.c2c/weekly/kv50 failed with artifacts on master @ aa85c69776da942b4d539891725b780ba995401e:
Parameters: Help
See: roachtest README See: How To Investigate (internal) Grafana is not yet available for aws clusters |
So we attempt to fingerprint from |
113501: roachtest: bump GC TTL on source and dest tenant ranges for weekly roachtest r=msbutler a=adityamaru Previously, the kv50 weekly roachtest would take >4 hours, the default GC TTL, to complete replication and cutover. Thus, by the time fingerprinting would run some of the keys would already be under the GCThreshold before the FP machinery got a chance to write a PTS. To work around this we bump the GC TTL on the source and dest tenant ranges to 12 hours, the timeout of the roachtest. Fixes: #112823 Release note: None Co-authored-by: adityamaru <[email protected]>
…achtest Previously, the kv50 weekly roachtest would take >4 hours, the default GC TTL, to complete replication and cutover. Thus, by the time fingerprinting would run some of the keys would already be under the GCThreshold before the FP machinery got a chance to write a PTS. To work around this we bump the GC TTL on the source and dest tenant ranges to 12 hours, the timeout of the roachtest. Fixes: #112823 Release note: None
roachtest.c2c/weekly/kv50 failed with artifacts on master @ 07915532f9a7def000127029c667c3a91ce90e47:
Parameters:
ROACHTEST_arch=amd64
,ROACHTEST_cloud=aws
,ROACHTEST_cpu=8
,ROACHTEST_encrypted=false
,ROACHTEST_fs=ext4
,ROACHTEST_localSSD=false
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
Grafana is not yet available for aws clusters
This test on roachdash | Improve this report!
Jira issue: CRDB-32617
The text was updated successfully, but these errors were encountered: