We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Now that TRUNCATE is part of the topology state machine, we need a TRUNCATE Nemesis which would work togegher with other topology nemeses in SCT.
We need to test that truncate works fine with add/remove/replace/etc topology ops under load.
Tablets only for now, since new truncate implementation is tablets only.
The text was updated successfully, but these errors were encountered:
isn't disrupt_truncate and disrupt_truncate_large_partition do exactly that ?
disrupt_truncate
disrupt_truncate_large_partition
Sorry, something went wrong.
kostja
No branches or pull requests
Now that TRUNCATE is part of the topology state machine, we need a TRUNCATE Nemesis which would work togegher with other topology nemeses in SCT.
We need to test that truncate works fine with add/remove/replace/etc topology ops under load.
Tablets only for now, since new truncate implementation is tablets only.
The text was updated successfully, but these errors were encountered: