Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 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

Assigned Teams:

Replication
Backwards Compatibility:
Minor Change
Operating System:
ALL
Backport Requested:

v8.0, v7.3, v7.0
Sprint:
Repl 2023-09-18, Repl 2023-10-02, Repl 2023-10-16, Repl 2023-10-30, Repl 2023-11-13, Repl 2023-11-27
Case:
Linked BF Score:
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

SERVER-83193 Replace deprecated BatchedCommandRequest getters/setters for WC with the ones provided by OperationContext

Closed

SERVER-76351 Improve readability of write concern defaults

Backlog

is related to

SERVER-88305 BatchRequest should not parse supplied write concern if missing 'w' field

Closed

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

(1 related to)

Assignee:: Moustafa Maher

Reporter:: Asya Kamsky

Participants:: Asya Kamsky, Githook User, Judah Schvimer, Max Hirschhorn, Moustafa Maher, Samyukta Lanka

Votes:: 0 Vote for this issue

Watchers:: 20 Start watching this issue

Created:: Aug 23 2023 10:43:23 PM UTC

Updated:: Apr 12 2024 07:52:30 AM UTC

Resolved:: Nov 22 2023 01:58:11 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates