-
Notifications
You must be signed in to change notification settings - Fork 4.1k
roachtest: assert replica data consistency checks after tests #115770
Copy link
Copy link
Closed
Labels
A-testingTesting tools and infrastructureTesting tools and infrastructureC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)branch-release-23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2v23.2.1
Metadata
Metadata
Assignees
Labels
A-testingTesting tools and infrastructureTesting tools and infrastructureC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)branch-release-23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2v23.2.1
Roachtests run a consistency check after each test, but this is only for stats divergence, not for actual data divergence, and with a 5 minute timeout it doesn't have time to check a lot of data.
We should run a full consistency check after each test, and also preserve the checkpoints on any divergence, to improve coverage of replica divergence as seen in e.g. #114421.
Jira issue: CRDB-34201