-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 7.3.0-rc0
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
v7.3, v7.0, v6.0, v5.0
-
CAR Team 2024-02-05, CAR Team 2024-03-18, CAR Team 2024-04-01
-
9
-
2
BatchedCommandRequest is the legacy (pre-IDL) way that write commands were parsed by MongoS and constructed to be sent to MongoD. At that time there wasn't write concern on the OpContext (there wasn't generic parsing of WC on the MongoS to be more specific) so each request had to parse and store it.
Now that the opCtx has become the "official holder" of WC options, the related methods of BatchedCommandRequests should be retired, as WC values stored in them are no longer guaranteed to be honoured.
- causes
-
SERVER-88833 mongos generates a reply for writes sent by client with w:0
- Closed
- depends on
-
SERVER-80363 server default writeConcern is not honored when wtimeout is set
- Closed
- is related to
-
SERVER-88305 BatchRequest should not parse supplied write concern if missing 'w' field
- Closed