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

Make sure we don't retry non-idempotent writes on "NotMaster" errors that actually did a write

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Sharding
    • None
    • Fully Compatible
    • ALL
    • Repl 18 (08/05/16), Repl 2016-08-29

      Generally if you get a NotMaster error back from an attempted write you know that nothing was written. With SERVER-24574, however, it's possible for a node that steps down mid-write to actually return NotMaster to the client. When we write to the config servers, we retry non-idempotent writes on NotMaster errors because we assume no write actually happened, but that assumption is now invalid, so the retries can lead applying a non-idempotent write multiple times.

            Assignee:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: