-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Fully Compatible
-
ALL
-
Execution Team 2021-10-04
-
27
With lock-free reads and SBE, it is now possible for operations to fail due to a concurrent full validation. Usually our tests don't run full validation on a collection concurrently with other operations, but certain suites can do this with a concurrent tenant migration or chunk migration. This results in a failure of the operation that is not expected by the test, but is expected behavior.
There are a couple of possible cases here:
- Tests that manually run full validation, like doc_validation_encrypt_keywords.js
- Test infrastructure which runs full validation
- is related to
-
SERVER-63945 test_resharding_test_fixture_shutdown_retry_needed.js can run full validation concurrently with resharding
- Closed
-
SERVER-63946 tenant_migration_donor_resume_on_stepup_and_restart.js can run full validation concurrently with tenant migration
- Closed
- related to
-
SERVER-60006 Investigate throwing WriteConflictException on EBUSY in WiredTigerSession::getNewCursor
- Closed