kv: perturbation test for intent resolution #135937
Labels
A-admission-control
A-kv-transactions
Relating to MVCC and the transactional model.
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-kv
KV Team
Is your feature request related to a problem? Please describe.
In a customer case, we saw almost 10 billion intents created over multiple ranges over a 5 hour window from a single INSERT INTO ... SELECT FROM statement that was ultimately aborted. We should create a perturbation test that simulates this behavior and validates that whether the intents are cleaned up by either a conflicting higher priority transaction or the mvcc gc queue.
Describe the solution you'd like
We have seen large availability outages due to LSM inversion when the mvcc gc queue cleaned up these intents.
Describe alternatives you've considered
There is an existing test
registerIntentResolutionOverload
which tests that the LSM does not get too overloaded. We can replace this test with a perturbation test.Jira issue: CRDB-44796
The text was updated successfully, but these errors were encountered: