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

Pause the oplog visibility thread in mode SECONDARY

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Execution Team 2019-06-17, Execution Team 2019-11-04, Execution Team 2019-11-18

      In secondary mode, secondary batch application logic already handles visibility and holes in the oplog. Both the in-memory oplogReadTimestamp and the persisted oplogTruncateAfterPoint are updated. There's no need for the oplog visibility thread to run and use resources doing unnecessary work. (plus it would get confusing with batch application unsetting the oplogTruncateAfterPoint while the oplog visibility thread keeps setting it)

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: