Re: Prefetch maintenance might lead to thundering herd issues
- From
Derrick Stolee <stolee@gmail.com>
- Date
- Sep 23, 2024, 01:26 UTC
- Message-ID
- <91bf8c63-b2fc-48ca-a6de-37a576ddc1b1@gmail.com>
- In-Reply-To
- <CAG=Um+2g-pn3XmC4MVkA+UAGeWpHw5U6fe=zXR=6-ibu3d0qsg@mail.gmail.com>
On 9/22/24 2:40 PM, Shubham Kanodia wrote:
> On Sat, Sep 21, 2024 at 1:20 AM Derrick Stolee <stolee@gmail.com> wrote:
Show 5 quoted lines
>> This is already handled by using a random minute of the hour, as >> implemented in 9b43399057 (maintenance: use random minute in cron >> scheduler, 2023-08-10), for example. There are similar uses for >> systemd, launchctl, and schtasks schedulers (look for uses of >> the get_random_minute() method).
Show 9 quoted lines
> Ah, thanks for pointing that out. It wasn't really clear from the > multiple examples and cron expressions on the git > maintenance documentation page (which have examples such as `0 1-23 * > * *` for hourly). I should've looked > more deeply into the implementation. > > Perhaps adding a line to the existing doc might be of help? What do > you think about adding a line to the > section on scheduling —
I do think a doc change would help. Please submit it as a patch for review!
Thanks, -Stolee