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

Uncommitted write visible with 'majority' readConcern after rollback

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 13 (04/22/16)

      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.

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

              Created:
              Updated:
              Resolved: