[SERVER-58506] Command to expose settability for Server Parameters Created: 14/Jul/21 Updated: 08/Jan/24 Resolved: 26/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.8, 5.3.0, 4.4.15, 4.2.21 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | George Wangensteen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | original-top-20, servicearch-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||||||
| Backport Requested: |
v5.2, v5.1, v5.0, v4.4, v4.2
|
||||||||||||||||||||||||||||
| Sprint: | Service Arch 2021-12-13, Service Arch 2022-1-10, Service Arch Test, Service Arch 2022-1-24, Service Arch 2022-2-07 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Story Points: | 4 | ||||||||||||||||||||||||||||
| Description |
|
Currently there's no way from outside of a running mongo process to tell whether a given server parameter controlled via get/setParameter is settable at runtime (vs. just at startup). Providing a mechanism to access that information (either by altering getParameter, or with a new command) would make it easier to write tools like the automation agent by making the requirements around altering a setParameter much more discoverable. Acceptance Criteria The goal here would be command that could be invoked to:
|
| Comments |
| Comment by Melissa Plunkett [ 22/Apr/22 ] |
|
Wonderful news on a Friday, thank you blake.oler@mongodb.com! |
| Comment by Githook User [ 22/Apr/22 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: (cherry picked from commit aae909d4cfba1621ccaf5d6168b89a0577d4e0ca) |
| Comment by Githook User [ 21/Apr/22 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: (cherry picked from commit aae909d4cfba1621ccaf5d6168b89a0577d4e0ca) |
| Comment by Githook User [ 19/Apr/22 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: (cherry picked from commit aae909d4cfba1621ccaf5d6168b89a0577d4e0ca) |
| Comment by George Wangensteen [ 15/Mar/22 ] |
|
We discussed offline - still planning on backporting this to all LTS branches after 5.3 is released |
| Comment by Melissa Plunkett [ 15/Mar/22 ] |
|
george.wangensteen we just noticed our discussed backports are missing? Can you let me know what's going on here? |
| Comment by Melissa Plunkett [ 26/Jan/22 ] |
|
george.wangensteen further thank you for sharing the functionality here! This will be a huge help in improving the user experience for our customers. Thanks to you and the team! |
| Comment by Melissa Plunkett [ 26/Jan/22 ] |
|
george.wangensteen 5.3 should be sufficient. thank you! cc louisa.berger |
| Comment by Githook User [ 26/Jan/22 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |
| Comment by George Wangensteen [ 19/Jan/22 ] |
|
melissa.plunkett I just took a look and I think that should be doable. I will request backports for 5.2, 5.1, 5.0, 4.4., and 4.2 and attempt to do so and let you know if there are any issues. |
| Comment by Melissa Plunkett [ 19/Jan/22 ] |
|
george.wangensteen our ideal scenarios - to have the most impact - would be back to 4.2. Is that possible? |
| Comment by Melissa Plunkett [ 17/Nov/21 ] |
|
Fantastic news, thank you for the alert lauren.lewis |
| Comment by Lauren Lewis (Inactive) [ 16/Nov/21 ] |
|
shameek.ray raised this as a major value add for Cloud, slating for upcoming sprint. cc: melissa.plunkett |