Create a concurrency workload that runs migrations and updates to the shard key value simultaneously.
- depends on
-
SERVER-40898 Transaction table updates may be applied out of order when retryable writes and transactions are in the same secondary batch
- Closed
-
SERVER-41052 Add shard key change context to DuplicateKey errors in the findAndModify path
- Closed
-
SERVER-41074 Don't migrate prePostImageDoc session entries for CRUD operations outside of current migration range
- Closed
-
SERVER-41078 Make replica set primary detection stepdown-proof in concurrency workloads
- Closed
-
SERVER-39940 Model a shard key update as a delete inside the chunk migration cloner if the document moves out of a currently-migrating chunk
- Closed