[SERVER-56961] [v4.4] Ensure cluster is in FCV 4.4 while running FuzzerRestoreClusterSettings hook Created: 14/May/21 Updated: 29/Oct/23 Resolved: 17/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| 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 | ||||||||||||||||||||
| Sprint: | Sharding 2021-05-17 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 70 | ||||||||||||||||||||
| Description |
|
The setDefaultRWConcern command run by the run_fuzzer_restore_cluster_settings.js hook is only allowed in FCV 4.4. We should ensure the cluster is in FCV 4.4 before attempting to run the setDefaultRWConcern command. Note that it isn't sufficient to skip running the setDefaultRWConcern command when the server isn't in FCV 4.4 because it is possible for the FCV 4.2 downgrade to have been interrupted and for the cluster-wide default read and write concerns to still be set to nonsensical values by the fuzzer. |
| Comments |
| Comment by Githook User [ 17/May/21 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |