You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running rqworker --with-scheduler (django-rq), after I restart the server (e.g., during deploy), I notice that it takes a while before scheduled tasks are enqueued - the docs state, "Idle schedulers will periodically (every 15 minutes) check whether the queues they’re responsible for have active schedulers." Is this the cause of the delay we see (the delay seems to range from a few minutes to 10 minutes)? When starting via --with-scheduler is there a way to tell the system to start running the scheduler immediately, so that queued up tasks that come due are run without that multi-minute delay?
P.S. @selwin - pardon the duplicate notification - I started to piggyback this on a scheduler-related issue, to avoid making a new issue, but immediately realized I was co-opting the other issue's subject by doing so.
The text was updated successfully, but these errors were encountered:
When a worker() first starts, it already tries to acquire scheduler locks so in your case, the lock was probably still active when your workers started.
One way we can make the delay in acquiring schedulers shorter is by reducing the maintenance task interval to 5 minutes (it was initially 15 minutes and now 10 minutes).
When running
rqworker --with-scheduler
(django-rq
), after I restart the server (e.g., during deploy), I notice that it takes a while before scheduled tasks are enqueued - the docs state, "Idle schedulers will periodically (every 15 minutes) check whether the queues they’re responsible for have active schedulers." Is this the cause of the delay we see (the delay seems to range from a few minutes to 10 minutes)? When starting via--with-scheduler
is there a way to tell the system to start running the scheduler immediately, so that queued up tasks that come due are run without that multi-minute delay?P.S. @selwin - pardon the duplicate notification - I started to piggyback this on a scheduler-related issue, to avoid making a new issue, but immediately realized I was co-opting the other issue's subject by doing so.
The text was updated successfully, but these errors were encountered: