linearizable read concern does not check if node is still primary before it writes noop

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.4.0-rc4
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2016-11-21
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a stepdown occurs here, the noop write will still occur even though the node is now a secondary, leading to an inconsistent state: https://github.com/mongodb/mongo/blob/e82b201cf7d17f64f54b57f58dc9668527ab49b1/src/mongo/db/read_concern.cpp#L138-L142

              Assignee:
              Judah Schvimer
              Reporter:
              Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: