[SERVER-33024] ReplCoord::getMyLastAppliedOpTime might not be set when clearing the initial sync flag Created: 30/Jan/18  Updated: 29/Oct/23  Resolved: 04/Feb/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.7.2

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng, rollback-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-02-12
Participants:

 Description   

Clearing the initial sync flag makes a write to the minvalid document. This write is timestamped at the lastApplied timestamp

However, if initial sync had no oplog window to apply, this call to `clearInitialSyncFlag` may not be timestamped.



 Comments   
Comment by Githook User [ 04/Feb/18 ]

Author:

{'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb', 'username': 'dgottlieb'}

Message: SERVER-33024: Set last applied when coming out of initial sync.

An initial sync can complete when without needing to go through an oplog
application phase. In that case, last applied is not set.
Branch: master
https://github.com/mongodb/mongo/commit/216c0f863225609a67a3dcecab3cf0f8d884f511

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