-
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
-
None
-
Fully Compatible
-
ALL
-
v6.2, v6.0, v5.0, v4.4
-
-
Sharding NYC 2022-11-28, Sharding 2022-12-12, Sharding NYC 2022-12-26, Sharding NYC 2023-01-09, Sharding NYC 2023-01-23, Sharding NYC 2023-02-06
-
113
Migration relies on LogTransactionOperationsForShardingHandler to capture writes that gets committed. However, the issue is that the commit handler only gets registered to the recovery unit during prepare. This means that if another node becomes the primary, no callbacks from LogTransactionOperationsForShardingHandler will get called when the transaction gets committed.
- causes
-
SERVER-78050 Chunk Migration Can Lose Data If Processing Deferred Modifications
- Closed
- is related to
-
SERVER-68361 LogTransactionOperationsForShardingHandler::commit misses transferring documents from prepared and non-prepared transactions changing a document's shard key value
- Closed
-
SERVER-38284 Remove donor collection X-lock acquisition for starting the clone phase
- Closed