[DOCS-16510] Investigate changes in SERVER-80363: server default writeConcern is not honored when wtimeout is set Created: 22/Nov/23  Updated: 22/Jan/24  Resolved: 08/Dec/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.3.0-rc0, 7.0.5, 7.2.1, Server_Docs_[20240122]

Type: Task Priority: Minor - P4
Reporter: Backlog - Core Eng Program Management Team Assignee: Lauren Tran
Resolution: Done Votes: 0
Labels: feature
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backported by DOCS-16585 [BACKPORT] [v7.2] server default writ... Closed
Documented
documents SERVER-80363 server default writeConcern is not ho... Closed
Related
is related to DOCS-16526 [BACKPORT] [v7.0] server default writ... Closed
Participants:
Days since reply: 11 weeks, 1 day ago
Story Points: 1

 Description   
Original Downstream Change Summary
  • Explicitly documenting that missing 'w' field from write concern object will be filled with default write concern.
  • 'w' field is not optional while setting default write concern using setDefaultRWConcern command

    Description of Linked Ticket

    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.


Generated at Thu Feb 08 08:15:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.