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

Majority (WC) writes, even no-ops, must enforce replication WC

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.7
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • RPL 7 08/10/15
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      On the server enforcing the write concern, the primary replica member, if no write is done then it should enforce a majority write concern on the latest system write.

      This is needed so the client can then read the post-state of that write, or something newer. It is especially important if a client needs to retry a write due to a network interruption waiting for the response – if the client then retries the operation, it will look like a no-op to the server, but the write concern still needs to wait until the original write has replicated appropriately.

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            scotthernandez Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: