read concern level majority checking is racy

XMLWordPrintableJSON

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

      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:
              Eric Milkie
              Reporter:
              Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: