-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
v4.4
-
Sharding 2020-04-20
-
18
So that it won't fail if the previous default write concern is not satisfiable. Because the writeConcern setting is extracted before the command is executed, it can end up using the default writeConcern before the reset when waiting for writeConcern at the end of the command.
- is duplicated by
-
SERVER-47520 Fuzzer must specify w: 1 when unsetting CWRWC
- Closed
- related to
-
SERVER-46947 Add cleanup fuzzer hook to undo undesired settings from fuzzer
- Closed