[SERVER-80251] Re-evaluate condition for reading at last applied for the oplog Created: 18/Aug/23  Updated: 06/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Sprint: Execution NAMR Team 2023-10-02, Execution Team 2024-04-01
Participants:

 Description   

The shouldReadAtLastApplied function returns whether the current operation should read at the last applied timestamp based on several criteria including namespace and replication state. One of the conditions is if we are reading from the oplog on a secondary, we return true (indicating that we should read at the last applied timestamp). However, it's not immediately clear what this means since writes to the oplog collection are not timestamped. We should re-evaluate this condition.


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