Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Sharding NYC
-
Fully Compatible
-
Sharding NYC 2023-03-06, Sharding NYC 2023-03-20
-
5
Description
This code is incompatible with catalog shards and after discussions can be removed. This will probably be a multi step process:
- Make sure any calls that might use this code path are explicitly specifying the writeConcern
- assert the above behaviour i.e if check if there are any edge cases we missed
- remove the code
- downstream attention (mongorestore, automation agent etc etc)
Attachments
Issue Links
- is depended on by
-
TOOLS-3272 Investigate changes in SERVER-67874: Remove config server code which upconverts all writeConcern to majority
-
- Closed
-
-
COMPASS-6607 Investigate changes in SERVER-67874: Remove config server code which upconverts all writeConcern to majority
-
- Closed
-
- is related to
-
SERVER-34212 Config servers should only upconvert writeConcern to majority for requests on internal connections
-
- Closed
-
-
SERVER-34501 Remove the config server code which upconverts all writeConcern to majority
-
- Closed
-