-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Fully Compatible
-
ALL
-
Security 2022-01-24, Replication 2021-12-13, Replication 2021-12-27, Replication 2022-01-10
-
(copied to CRM)
-
167
setDefaultRWConcern accepts invalid write concern options like {w: "1"}, but the server will error with UnknownReplWriteConcern when trying to do an actual write.
We should either start accepting {w: "1"} or error at the time of setting the default read/write concern.
- is related to
-
SERVER-61864 Replica set reconfiguration should check it's not removing a custom write concern which is set as the default
-
- Closed
-
- related to
-
-
- Open
-
-
SERVER-64309 Modify the server to support the setRWConcernDefault command directly against shardsvrs
-
- Closed
-