[SERVER-47500] run_fuzzer_restore_cluster_settings.js should explicitly specify w:1 Created: 13/Apr/20  Updated: 29/Oct/23  Resolved: 14/Apr/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.4.0-rc2, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-47520 Fuzzer must specify w: 1 when unsetti... Closed
Related
related to SERVER-46947 Add cleanup fuzzer hook to undo undes... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Sharding 2020-04-20
Participants:
Linked BF Score: 18

 Description   

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.



 Comments   
Comment by Githook User [ 16/Apr/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-47500 Specify writeConcern:

{w: 1}

in run_fuzzer_restore_cluster_settings.js

(cherry picked from commit 3755ee11d537fe42781c88031790b2bbb34b1d1c)
Branch: v4.4
https://github.com/mongodb/mongo/commit/709fecfc02190395b73849d5a902eae8c170e421

Comment by Githook User [ 14/Apr/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-47500 Specify writeConcern:

{w: 1}

in run_fuzzer_restore_cluster_settings.js
Branch: master
https://github.com/mongodb/mongo/commit/3755ee11d537fe42781c88031790b2bbb34b1d1c

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