Open
Conversation
|
This would definitely have helped me to realize why my once-per-minute jobs, scheduled with a crontab, were running at seemingly random seconds after each minute, instead of on the minute. It was because the polling was being done at 60-second intervals after the container booted up, and that boot-up time was a random number of seconds after the minute. I fixed it by setting rq-scheduler's polling interval to 1 second. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As per @mojeto #163 (comment)
I feel that this would clear up some issues around rq-scheduler usage, where folks would set a < 1 minute job interval, but it still running once a minute, and being confusing. Possible also issues with seeming "drift"?
Perhaps a maintainer can give good reasons for the following directives, then I can amend the doc: