-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
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
-
(copied to CRM)
-
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.
- is depended on by
-
-
- Closed
-
-
SERVER-76351 Improve readability of write concern defaults
-
- Backlog
-
- is documented by
-
DOCS-16510 Investigate changes in SERVER-80363: server default writeConcern is not honored when wtimeout is set
-
- Closed
-
- is related to
-
-
- Closed
-
-
DRIVERS-2074 Should we parse wtimeoutMS when w <= 1?
-
- Backlog
-
- related to
-
-
- Closed
-
-
-
- Closed
-