[SERVER-73553] Ensure mongos create command returns WriteConcern with higher precedence over NamespaceNotFound Created: 02/Feb/23  Updated: 26/Oct/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Xuerui Fa Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-60933 Make the sharded cluster's 'create' c... Closed
Related
is related to SERVER-78311 mongos does not report writeConcernEr... Closed
is related to SERVER-80103 Mongos WriteConcernError Behavior Dif... Needs Scheduling
Assigned Teams:
Catalog and Routing
Participants:
Story Points: 2

 Description   

Problem

In the mongos create cmd code, we currently may return the createStatus error over any WriteConcern errors. This may lead to incompatibilities where we expect to retry on a WriteConcern error, but instead we fail due to the createStatus error being returned first.

Solution & Acceptance Criteria

We should prioritize sending any WriteConcern errors over other errors

Impact

This change leads to clearer and safer usage of the create command. It will also allow us to remove a workaround in mongosync where we manually handle NamespaceNotFound since it is send instead of a WriteConcern error


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