Don't start the oplog manager thread in standalone mode

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Oplog visibility is not used in standalone mode and the read timestamp is set to the maximum value. Despite this, the background thread used to update the read timestamp was still created and would go through the process of updating after every write (only to do nothing as it never decreases the read timestamp).

            Assignee:
            Thomas Goyne
            Reporter:
            Thomas Goyne
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: