[DOCS-16320] Investigate changes in SERVER-78913: Make the periods of query sampling periodic jobs configurable at runtime Created: 16/Aug/23 Updated: 13/Nov/23 Resolved: 12/Sep/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Joseph Dougherty |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | query, release | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 25 weeks ago | ||||||||
| Description |
|
Original Downstream Change Summary Starting from 7.0.1 (not released yet), the queryAnalysisSamplerConfigurationRefreshSecs and queryAnalysisWriterIntervalSecs server parameters are configurable at runtime (i.e. not just on startup). Description of Linked TicketCurrently, the server parameters for the periods of the periodic jobs for refreshing query sampling configurations and writing sampled queries to disk are configurable on startup only. Although users are unlikely to need to configure these periods, we should still make them configurable in runtime. Here is an example of how to subscribe to changes to a server parameter, and here is an example of how the period of a PeriodicRunner::Job can be updated. |