-
Type: Bug
-
Resolution: Fixed
-
Priority: Critical - P2
-
Affects Version/s: 4.2.0, 4.4.0, 5.0.0, 6.0.0, 6.1.0-rc3
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
v6.1, v6.0, v5.0, v4.4, v4.2
-
Sharding 2022-08-08, Sharding 2022-08-22, Sharding 2022-09-05, Sharding 2022-09-19, Sharding NYC 2022-11-14
-
113
-
5
Original summary
Investigate getPreImageDocumentKey calls in LogTransactionOperationsForShardingHandler::commit
Original description
It is called a few times around here:
https://github.com/mongodb/mongo/blob/119e6b5979e4b1e8fcf91db711673393c56b4020/src/mongo/db/s/migration_chunk_cloner_source_legacy.cpp#L240
But there appears to be no code setting the value.
- is caused by
-
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
- is related to
-
SERVER-40791 Chunk migration clone blocks behind prepared transactions
- Closed
-
SERVER-71028 MigrationChunkClonerSourceLegacy::nextCloneBatch should ignore prepare conflict
- Backlog
- related to
-
SERVER-71219 Migration can miss writes from prepared transactions
- Closed
-
SERVER-70152 PeekableCursor's definition of hasNext() ignores the state of the stashed document
- Closed