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

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

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

      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@mongodb.com Judah Schvimer
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: