Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:
- 9.0-api-parity
- cs-correctness

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Cluster Scalability 2024-12-23
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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-98462 mongos parity: Some commands return different values compared to replica-set

Backlog

SERVER-98461 findAndModify where query does not have shard key does not return WCE on failure

Closed

SERVER-97226 dropIndexes command suppresses write concern errors.

Closed

SERVER-97564 mongos does not return WriteConcernError in renameCollection

Closed

SERVER-97773 mongos suppresses WriteConcernError in findAndModify

Closed

SERVER-97774 mongos suppresses WriteConcernError for dropDatabase, drop (collection)

Closed

SERVER-97780 mongos suppresses WriteConcernError in create

Closed

SERVER-98602 mongos suppresses WriteConcernError for findAndModify

Closed

SERVER-98603 findAndModify on unsharded coll vs. sharded coll returns different results

Closed

SERVER-97754 User-provided write concern is not honored for DDL operations on sharded clusters (always w:majority)

Needs Scheduling

related to

SERVER-97470 findAndModify: Mongos WriteConcernError Behavior Differs from Mongod

Closed

SERVER-73553 Ensure mongos create command returns WriteConcern with higher precedence over NamespaceNotFound

Closed

SERVER-78311 MongoS does not report writeConcernError in presence of writeErrors for insert command

Closed

SERVER-97471 drop/dropDatabase: Mongos WriteConcernError Behavior Differs from Mongod

Closed

(6 is related to, 4 related to)

Assignee:: Israel Hsu (Inactive)
Reporter:: Brett Nawrocki
Participants:: Brett Nawrocki, Githook User, Israel Hsu
Votes:: 0 Vote for this issue
Watchers:: 11 Start watching this issue

Created:: Aug 15 2023 07:47:17 PM UTC
Updated:: Feb 13 2025 08:29:47 PM UTC
Resolved:: Dec 20 2024 02:50:20 AM UTC
Confidence Status Last Update:: 21/Nov/24 9:30 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates