Block read committed reads after metadata changes, rather than returning an error

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.7
    • Affects Version/s: None
    • Component/s: Querying, Replication
    • None
    • Fully Compatible
    • RPL 8 08/31/15
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After making a metadata change, even if the writer waits for w:majority write concern, a subsequent read concern level majority read to a secondary node may return an error ReadMajorityNotAvailableYet, if that node has not yet produced and blessed a snapshot as the committed snapshot after the metadata change was applied.
      Instead, the read should block until such a snapshot is available.

              Assignee:
              Matt Dannenberg (Inactive)
              Reporter:
              Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: