-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Cluster Scalability
-
ALL
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.
- depends on
-
SERVER-78311 mongos does not report writeConcernError in presence of writeErrors for insert command
- Closed
- is related to
-
SERVER-97226 dropxIndexes command suppresses write concern errors.
- Backlog
- related to
-
SERVER-73553 Ensure mongos create command returns WriteConcern with higher precedence over NamespaceNotFound
- Open
-
SERVER-78311 mongos does not report writeConcernError in presence of writeErrors for insert command
- Closed
-
SERVER-97470 findAndModify: Mongos WriteConcernError Behavior Differs from Mongod
- Needs Scheduling
-
SERVER-97471 drop/dropDatabase: Mongos WriteConcernError Behavior Differs from Mongod
- Needs Scheduling