-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
MigrationChunkClonerSourceLegacy::nextCloneBatch should ignore prepare conflict when fetching documents.
Otherwise, they will end up unnecessarily waiting for prepare conflict to get resolved. It is okay for migration to ignore prepare conflicts because it already captures all ongoing modifications to documents in the chunk range that will end up getting committed.
- related to
-
SERVER-68361 LogTransactionOperationsForShardingHandler::commit misses transferring documents from prepared and non-prepared transactions changing a document's shard key value
- Closed
-
SERVER-40791 Chunk migration clone blocks behind prepared transactions
- Closed
-
SERVER-76546 _migrateClone can deadlock with prepared transactions on secondaries
- Closed