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

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.2, 4.1.3
    • Replication
    • None
    • Fully Compatible
    • v4.0
    • Repl 2018-08-13, Repl 2018-08-27
    • 68

    Description

      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.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-39497 Revert SERVER-33248

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-32166 Do not clear sync source when going from RECOVERING to SECONDARY

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34855 Blacklist restart_catalog.js from causal consistency suites

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-39367 lastOpCommitted being reset on restart can cause sync source cycle

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-40193 Do not propagate commit point through heartbeats when FCV=4.0

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-40194 Revert SERVER-33248 on 4.0

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: