[SERVER-81381] Wait lastStableRecoveryTimestamp to pass atClusterTime in resharding cloner Created: 22/Sep/23  Updated: 29/Oct/23  Resolved: 09/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.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-10-02, Repl 2023-10-16
Participants:
Linked BF Score: 138

 Description   

We are now relying on the resumeToken to clone data, if the donor restarts in the middle and lastStableRecoveryTimestamp is smaller than the snapshot time we are reading, the donor will reconstruct the collection by reapplying oplogs, which will lead to a different physical layout and the resumeToken will point to something non-exist or wrong.



 Comments   
Comment by Githook User [ 09/Oct/23 ]

Author:

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

Message: SERVER-81381 Add waitLastStableRecoveryTimestamp in read concern to ask donor to wait before serving snapshot read
Branch: master
https://github.com/mongodb/mongo/commit/5d5aa68a06425de92dd8c8f21dde7a7e05ace38c

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