with default write concern (no getLastError), if master changes in repl set, small edge case where writes will fail undetected

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.5
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In case or reads, we always get an answer back from db and if it's an error saying "not master", we do a force check master.
      But for writes, with default setting, client never gets an answer back and the error goes unnoticed.
      A clean fix would be to have updater thread do a forced checkmaster.
      This way the max we lose is 5s worth of docs.. which is ok for w=0.

            Assignee:
            Antoine Girbal (Inactive)
            Reporter:
            Antoine Girbal (Inactive)
            None
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: