#854·node-cron

Add randomness to execution time

Author: mwgambleCreated Feb 15, 2024Updated May 28, 2024
Labelstype:feature

⭐ Suggestion

The RandomizedDelaySec option for systemd timers: https://www.freedesktop.org/software/systemd/man/latest/systemd.timer.html#RandomizedDelaySec=

Use Cases

We have a job that needs to run once a day. We have several instances of this job running across multiple containers, and we'd like to spread the jobs out a bit. The jobs are all scheduled to run at (for the sake of an example) 8pm, but they don't actually all need to run at 8pm, they just need to run at around that time. It would be nice if we could configure a window of time (say 5-10 minutes) around which the job could run, so that they wouldn't all fire at once. This would help us avoid hitting some rate limits with a third-party API.

❌ Related Problems

We're hitting rate limits on a third-party API because we're doing too much simultaneously across all of the application's containers.