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

Do not update committed snapshot with null OpTime

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.1.7
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2019-01-14
    • 45

    Description

      When enableMajorityReadConcern='false', the stable optime can be ahead of the last committed optime, so the replication coordinator updates the committed snapshot based on the last committed optime instead of the stable optime. This causes a crash if the last committed optime is null, since _updateCommittedSnapshot_inlock() expects a non-null optime. We should not call _updateCommittedSnapshot_inlock() when the last committed optime is null.

      Attachments

        Activity

          People

            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: