[SERVER-80282] ReshardingCollectionCloner should only have one write thread for each donor shard Created: 21/Aug/23  Updated: 29/Oct/23  Resolved: 22/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Jiawei Yang Assignee: Jiawei Yang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2023-09-04
Participants:
Linked BF Score: 45

 Description   

If there are multiple threads inserting for the same donor shard, we can end up with writing an older batch later than writing a newer batch and break the resume token.

Check BF-29653 for more context



 Comments   
Comment by Githook User [ 22/Aug/23 ]

Author:

{'name': 'Jiawei Yang', 'email': 'jiawei.yang@mongodb.com', 'username': 'YoungYang0820'}

Message: SERVER-80282 ReshardingCollectionCloner should process batches from one donor using one thread
Branch: master
https://github.com/mongodb/mongo/commit/09d15ffcb3a82d93b6f12a40308b1a3064d860a5

Generated at Thu Feb 08 06:43:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.