[SERVER-36006] `multiInitialSyncApply` should consider setting a read timestamp of `kNoTimestamp` Created: 07/Jul/18  Updated: 29/Oct/23  Resolved: 20/Jul/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 4.0.0
Fix Version/s: 4.0.1

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: nyc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-35000 A RecoveryUnit::ReadSource of "no tim... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-07-30
Participants:
Linked BF Score: 0

 Description   

When SERVER-35000 was committed to master, the only oplog application method was multiSyncApply. However on 4.0, there was also multiInitialSyncApply. I believe this part of the patch is also intended to be applied to multiInitialSyncApply.



 Comments   
Comment by Githook User [ 20/Jul/18 ]

Author:

{'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}

Message: SERVER-36006 multiInitialSyncApply should set kNoTimestamp read source
Branch: v4.0
https://github.com/mongodb/mongo/commit/87df7df3dcef808f16481d969f1353446cb5a461

Generated at Thu Feb 08 04:41:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.