Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Critical - P2
Fix Version/s: 4.4.19, 5.0.15, 6.3.0-rc0, 6.0.5
Affects Version/s: 4.2.0, 4.4.0, 5.0.0, 6.0.0, 6.1.0-rc3
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v6.2, v6.0, v5.0, v4.4
Steps To Reproduce:

Hide

Uncomment this line in test

Show
Uncomment this line in test
Sprint:
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
Linked BF Score:
113
Confidence Status:
None
Work Order:
0
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Randolph Tan
Reporter:: Randolph Tan
Participants:: Githook User, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Nov 09 2022 06:19:18 PM UTC
Updated:: Oct 29 2023 09:30:50 PM UTC
Resolved:: Jan 27 2023 08:56:47 PM UTC
Confidence Status Last Update:: 09/Jan/23 3:46 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates