-
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
storage: manual testing of MVCC bulk ops #89276
Labels
Comments
cc @cockroachdb/replication |
erikgrinaker
changed the title
storage: Cyan testing of MVCC bulk ops
storage: manual testing of MVCC bulk ops
Oct 23, 2022
Ran a bunch of manual tests. Did not do exhaustive backup/restore tests, since these are covered by #89761. No serious issues were found, only these:
Rough notes, for posterity:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In lieu of proper end-to-end testing, we should do some manual testing of the new MVCC bulk ops work.
Enable relevant settings:
storage.mvcc.range_tombstones.enabled = true
kv.bulk_io_write.sst_rewrite_concurrency.per_call = 4
kv.bulk_io_write.sst_require_at_request_timestamp.enabled = true
gc.ttlseconds = 1800
sql.gc_job.wait_for_gc.interval = '1m'
First, test import cancellation into empty table:
SELECT *
,SELECT COUNT(*)
,SELECT * WHERE
).Next, test import cancellation into table with data:
Test schema changes where source has MVCC range tombstones:
Test backups:
Test GC:
Test PITR restores:
Jira issue: CRDB-20185
Epic CRDB-2624
The text was updated successfully, but these errors were encountered: