"Job Scheduler" Technique miss runs when using a non-default agent execution frequency
If we use a non standard agent execution frequency (more than 5 minutes), the job sheduler technique may not run jobs, as the splayclass(hourly) is only defined on a 5 minutes interval
Updated by François ARMAND over 4 years ago
Is there anything in CFEngine 3.6 that could help refactor that (quite hard) technique in a simpler way - and allows to remove that issue ?
There is also the question of the semantic we want to have for the missing runs: do we run them as soon as we saw that one is missing, or do we way for the next interval ? And of course, the second option must not lead to a "never run the job" if we are in the case matching the current issue (i.e, we have to be able to decide between "as close as we could have been for the job datetime - so ok, say it the same instant" from "we missed a job schedule, because perhaps the machine was down, what do we do with missed jobs ?")
Updated by Nicolas CHARLES 8 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis MOUSSET
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1370
Updated by Nicolas CHARLES 7 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|aa1ce5ba65b71b23267002b3e8ed0efce07b72f7.