[SERVER-84195] Handle the new lastWritten opTime in OplogQueryMetadata Created: 14/Dec/23  Updated: 02/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Wenbin Zhu Assignee: Pavithra Vetriselvan
Resolution: Unresolved Votes: 0
Labels: PM-3489-Milestone-LastWrittenOpTime-CP, PM-3489-perf-testing-required
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-83573 Update the lastWritten opTime during ... Closed
depends on SERVER-84190 Add lastWritten opTime to replication... Closed
depends on SERVER-84192 Add lastWritten opTime to OplogQueryM... Closed
is depended on by SERVER-85599 [Milestone] LastWritten OpTime Checkp... In Progress
Assigned Teams:
Replication
Sprint: Repl 2024-02-19
Participants:

 Description   

This is the follow-up work for SERVER-84192.

The OplogFetcher will need the new lastWritten to make certain decisions such as 
_checkRemoteOplogStart, and figuring out whether it should stop fetching (i.e. change sync source). The decision to change sync source may also rely on SERVER-84190 to populate lastWritten in the heartbeat responses.

SERVER-85705 may be a duplicate of this ticket, the assignee should double check it.


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