fork/django-q2
1
0
Fork 0
mirror of https://github.com/django-q2/django-q2.git synced 2026-09-15 13:37:56 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: moved Configuration to its own section

Browse Source 
* added more info on schedule catch up.
This commit is contained in:
Ilan
2015-08-19 12:38:15 +02:00
parent b99e16f108
commit 6610277b93
5 changed files with 201 additions and 184 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/schedules.rst
View File

@@ -41,6 +41,15 @@ You can manage them through the :ref:`admin_page` or directly from your code wit
minutes = 5,
next_run = arrow.utcnow().replace(hour=18, minute=0))
Missed schedules
----------------
If your cluster has not run for a while, the default behavior for the scheduler is to play catch up with the schedules and keep executing them until they are up to date.
For example, if your cluster was down for a day and you start it again. Any hourly schedules you had will run 24 times, once every schedule loop, until they are back in sync.
This behavior is intended to facilitate schedules that poll or gather statistics, but might not be suitable to your particular situation.
You can change this by settings the :ref:`catch_up` configuration setting to ``False``.
The scheduler will then skip execution of scheduled events in the past. Instead those tasks will run only once and normal scheduling resumes.
Management Commands
-------------------