[SERVER-35114] Make it possible to adjust the period of active jobs in the PeriodicRunner Created: 21/May/18 Updated: 29/Oct/23 Resolved: 29/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10, 4.0.12 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Mira Carey |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||||||
| Sprint: | Service Arch 2019-03-25, Service Arch 2019-04-08 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
There are startup+runtime settable server parameters that affect the period of jobs on the PeriodicRunner. Currently the periodic job to abort expired transactions uses a static variable hack inside the job to get around a non-adjustable job period. |
| Comments |
| Comment by Benjamin Caimano (Inactive) [ 30/Jul/19 ] |
|
Please note that while the functionality was backported, the integration with certain periodic jobs was not. |
| Comment by Githook User [ 30/Jul/19 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: (cherry picked from commit bf4a3cff4dc5572f2e97cb5279fe63c8227187e0)
(cherry picked from commit 1eff33bd1a8d48eb607675f87faf1836ba325006) This is a partial backport. Parts of the original commits listed do not |
| Comment by Githook User [ 29/Mar/19 ] |
|
Author: {'email': 'jcarey@argv.me', 'name': 'Jason Carey', 'username': 'hanumantmk'}Message: Add support for changing the period of a periodic job |
| Comment by Benjamin Caimano (Inactive) [ 26/Mar/19 ] |
|
Requesting a 4.0 backport because I believe this is trivial to backport and useful. |