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

read concern level majority checking is racy

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • 3.2.0-rc1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl B (10/30/15)
    • 0

      If setReadFromMajorityCommittedSnapshot() returns that there is no committed snapshot yet available, we then waitForNewSnapshot() and try again.
      There is a race between the two calls; if a snapshot is generated in between the two calls, and no further writes are made, then we will hang forever.

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: