Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-80251

Re-evaluate condition for reading at last applied for the oplog

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Execution NAMR Team 2023-10-02
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Unassigned Unassigned
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: