[SERVER-80103] Mongos WriteConcernError Behavior Differs from Mongod Created: 15/Aug/23  Updated: 30/Jan/24

Status: Needs Scheduling
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Brett Nawrocki Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: cs-subteam1, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-78311 mongos does not report writeConcernEr... Closed
Related
related to SERVER-73553 Ensure mongos create command returns ... Open
Assigned Teams:
Cluster Scalability
Operating System: ALL
Participants:

 Description   

The changes for SERVER-78311 introduces mongos_noop_writes_wait_for_write_concern.js, a variant of noop_writes_wait_for_write_concern.js that goes through mongos. SERVER-78311 addresses inconsistencies that caused the update/insert commands to fail, but there are still a number of commands whose tests cases are disabled due to differing behavior.

We should resolve these inconsistencies either directly or by filing additional tickets.


Generated at Thu Feb 08 06:42:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.