Write commands should not wait for replication if no write happened

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Write Ops
    • None
    • Minor Change
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a write command, say an update, doesn't result in any actual writes (i.e., nModified is 0 on an update), no new oplog entry is recorded, so it's not meaningful to wait for that operation to replicate. As such, write commands should never wait for replication if they have done no writes.

            Assignee:
            Scott Hernandez (Inactive)
            Reporter:
            Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: