Details
Description
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.
Attachments
Issue Links
- is depended on by
-
SERVER-83193 Remove write concern from the batched request
-
- Open
-
-
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
-
DRIVERS-2074 Should we parse wtimeoutMS when w <= 1?
-
- Backlog
-
- related to
-
SERVER-86116 CreateCollectionCoordinator may fail to create the chunk metadata on commit time.
-
- Closed
-
-
SERVER-86201 Cluster upserts performed through the ShardServerProcessInterface should use the operation context to configure their write concern
-
- Closed
-