Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Critical - P2
Fix Version/s: 8.1.0-rc0, 8.0.5
Affects Version/s: None
Component/s: Distributed Query Execution
Labels:
- 9.0-api-parity

Assigned Teams:

Query Execution
Backwards Compatibility:
Minor Change
Operating System:
ALL
Backport Requested:

v8.0, v7.0, v6.0
Sprint:
QE 2024-12-09, QE 2024-12-23

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.
This ticket is spawned off from ~~SERVER-80103~~ to investigate/address findAndModify.

is depended on by

COMPASS-8623 Investigate changes in SERVER-97470: findAndModify: Mongos WriteConcernError Behavior Differs from Mongod

Closed

TOOLS-3724 Investigate changes in SERVER-97470: findAndModify: Mongos WriteConcernError Behavior Differs from Mongod

Closed

is duplicated by

SERVER-97773 mongos suppresses WriteConcernError in findAndModify

Closed

is related to

SERVER-80103 Mongos WriteConcernError Behavior Differs from Mongod

Closed

related to

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

Closed

Assignee:: Jan Steemann

Reporter:: Adi Zaimi

Participants:: Adi Zaimi, Githook User, Jan Steemann

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: Nov 21 2024 04:14:47 PM UTC

Updated:: Jan 09 2025 10:02:06 AM UTC

Resolved:: Dec 11 2024 10:28:57 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates