[SERVER-47520] Fuzzer must specify w: 1 when unsetting CWRWC Created: 14/Apr/20  Updated: 06/Dec/22  Resolved: 14/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kevin Pulo Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-47500 run_fuzzer_restore_cluster_settings.j... Closed
Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

diff --git a/jstests/hooks/run_fuzzer_restore_cluster_settings.js b/jstests/hooks/run_fuzzer_restore_cluster_settings.js
index 0ffc864b621..92d641ae6d8 100644
--- a/jstests/hooks/run_fuzzer_restore_cluster_settings.js
+++ b/jstests/hooks/run_fuzzer_restore_cluster_settings.js
@@ -4,5 +4,5 @@
 // Unsetting read/write settings. This command will also cause the server to refresh and get
 // the new settings.
 assert.commandWorked(
-    db.adminCommand({setDefaultRWConcern: 1, defaultReadConcern: {}, defaultWriteConcern: {}}));
+    db.adminCommand({setDefaultRWConcern: 1, defaultReadConcern: {}, defaultWriteConcern: {}, writeConcern: {w: 1}}));
 })();


Generated at Thu Feb 08 05:14:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.