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

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

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.1.7
    • Querying, Replication
    • None
    • Fully Compatible
    • RPL 8 08/31/15
    • 0

    Description

      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.

      Attachments

        Activity

          People

            matt.dannenberg Matt Dannenberg
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: