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

getlasterror / writeconcern with a timeout should "fail fast" when that is possible

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Performance, Replication
    • None
    • Replication

    Description

      In theory the primary could know that secondaries are behind to much to possibly finish the current write in the timeout window specified by the caller of the getLastError command, and not wait to time out. this would likely improve stability of client apps as their entire conn pools would likely saturate if cluster is normally super responsive and then suddenly high timeout waits occur.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            dwight@mongodb.com Dwight Merriman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: