-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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: run clearrange test with range tombstones #88735
roachtest: run clearrange test with range tombstones #88735
Conversation
2cc0f1d
to
00962cc
Compare
I'm seeing the desired behaviour and elevated performance impact caused by clear range. This is because GC hint (#88336) is not merged. It should go back to being similar to what was there before after this pr is rebased on top of the change. |
Needs backport as we will converge to a single version once range tombstones become default, but this release will benefit from having two dedicated tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Previously clear range tests were run with default server settings. Range tombstones are disabled by default so new functionality in schema change commands is not execised. This commit adds test variant that enables range tombstones. Release note: None Fixes cockroachdb#86752
00962cc
to
e6a121b
Compare
bors r=erikgrinaker |
Build failed: |
bors r=erikgrinaker |
Build succeeded: |
Previously clear range tests were run with default server settings. Range tombstones are disabled by default so new functionality in schema change commands is not execised. This commit adds test variant that enables range tombstones.
Release note: None
Fixes #86752