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

Uncommitted write visible with 'majority' readConcern after rollback

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical - P2 Critical - P2
    • None
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 13 (04/22/16)

    Description

      Following a rollback, a secondary appears to mark it's new state as committed even if the primary hasn't confirmed that the write has been accepted by a majority of votes.

      See the attached test file, especially the XXX comments.

      Attachments

        Activity

          People

            milkie@mongodb.com Eric Milkie
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: