[SERVER-65809] Develop generalized mechanism for set[Cluster]Parameter FCV gating Created: 20/Apr/22 Updated: 29/Oct/23 Resolved: 22/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Varun Ravichandran | Assignee: | Gabriel Marks |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Security 2022-08-22, Security 2022-09-05, Security 2022-09-19, Security 2022-10-31, Security 2022-11-14, Security 2022-11-28 | ||||
| Participants: | |||||
| Description |
|
setClusterParameter and getClusterParameter are gated behind FCV 6.0, as implemented in Add a minimum FCV IDL option to server parameters. When set, if the FCV currently known to the server (note: mongos is unaware of the FCV, so this does not apply) is less than the set minimum FCV, the parameter will be disabled, and setParameter and getParameter will fail. For cluster server parameters, upon FCV downgrade, if the new FCV is less than the set minimum FCV, the parameter's value will be deleted from storage. Also, while getClusterParameter will still succeed on mongos if the cluster's FCV is less than the minimum FCV, setClusterParameter will fail in this case. |
| Comments |
| Comment by Githook User [ 17/Nov/22 ] |
|
Author: {'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}Message: |
| Comment by Githook User [ 17/Nov/22 ] |
|
Author: {'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}Message: |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |