[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: |
|
||||||||||||||||||||||||
| 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: in run_fuzzer_restore_cluster_settings.js (cherry picked from commit 3755ee11d537fe42781c88031790b2bbb34b1d1c) |
| Comment by Githook User [ 14/Apr/20 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: in run_fuzzer_restore_cluster_settings.js |