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

Allow choosing a sync source that we are up to date with if it has a higher lastOpCommitted

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.2, 4.1.3
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • v4.0
    • Repl 2018-08-13, Repl 2018-08-27
    • 68

      If you lose your sync source once you're up to date but before you update your lastOpCommitted, it can prevent secondary majority reads from progressing.

      This definitely needs to be investigated for how to do this correctly and safely.

            Assignee:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            3 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: