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

server default writeConcern is not honored when wtimeout is set

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.1, 7.3.0-rc0, 7.0.5, 6.0.15, 5.0.27
    • Affects Version/s: 6.0.9
    • Component/s: None
    • Labels:
      None
    • Replication
    • Minor Change
    • ALL
    • v8.0, v7.3, v7.0
    • Repl 2023-09-18, Repl 2023-10-02, Repl 2023-10-16, Repl 2023-10-30, Repl 2023-11-13, Repl 2023-11-27
    • 9

      Sending wtimeout:x without specifying w value causes the server to use w:1, wtimeout:x instead of combining wtimeout with server default (which should be majority in 5.0+).

      Reproduced with Java driver and mongo shell against 6.0. In the logs it indicates it received only wtimeout:xxx for writeConcern but it indicates it uses w:1 with passed wtimeout and claims it's provided by client.

            Assignee:
            m.maher@mongodb.com Moustafa Maher
            Reporter:
            asya.kamsky@mongodb.com Asya Kamsky
            Votes:
            0 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated:
              Resolved: