Test PromoteL0() with no concurrent PromoteL0() in stress test #12648
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context/Summary:
If any file on L0 that PromoteL0() called on were moved or deleted concurrently by another PromoteL0(), it will result and propagate to users the corruption
Corruption: VersionBuilder: Cannot delete table file #13 from level 0 since it is on level 3
to users. Such corruption will fail any subsequent writes. While it's debatable whether we should let such failure in PromoteL0() fail any subsequent writes, the easiest fix for now is to test PromoteL0() without any concurrent PromoteL0().Test:
CI that failed before this fix and pass after with equally frequent PromoteL0()