[SERVER-83573] Update the lastWritten opTime during secondary modes Created: 27/Nov/23  Updated: 25/Jan/24  Resolved: 10/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Wenbin Zhu Assignee: Jiawei Yang
Resolution: Fixed Votes: 0
Labels: PM-3489-Milestone-LastWrittenOpTime-CP
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-83093 Add functions in replication coordina... Closed
is depended on by SERVER-84195 Handle the new lastWritten opTime in ... Open
is depended on by SERVER-84196 Use lastWritten instead of lastApplie... Backlog
is depended on by SERVER-85599 [Milestone] LastWritten OpTime Checkp... In Progress
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2024-01-08, Repl 2024-01-22
Participants:

 Description   

This should include initial sync, rollback, oplog application, etc.



 Comments   
Comment by Githook User [ 10/Jan/24 ]

Author:

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

Message: SERVER-83573 Update lastWritten on secondary paths (#17820)

GitOrigin-RevId: 8ac7d9dc9eb996be57d46b02aa3a3e676ae4c102
Branch: master
https://github.com/mongodb/mongo/commit/5e4bb101a5c36dfdd843ec62ab31b85ffe11ed97

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