Comment 4 for bug 1319232
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to oslo-incubator (master) | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit c63fd5a439f22cf
Author: Matt Riedemann <email address hidden>
Date: Thu May 15 07:51:43 2014 -0700
Make unspecified periodic spaced tasks run on default interval
When there are multiple tasks with a defined spacing, they can get
somewhat staggered and force the periodic task processor to run
additional iterations. Since tasks with no spacing run every time the
periodic task processor runs, they get run more frequently than one
would expect.
Some may argue that this change in behavior could cause some task to
behave differently than it used to. However, there was never any
guarantee that the task would run more often than every 60 seconds, and
in many cases the tasks may already run less frequently than that (due
to other long-running tasks). So this change should not introduce any
new issues related to the timing of task execution; it would only serve
to make the timing more regular.
We should also make the default interval configurable but that's
reserved for a separate change.
DocImpact: periodic tasks without a specific spacing interval will now
run on the default interval (currently every 60 seconds) rather than
whenever the task processor runs.
UpgradeImpact: see above; periodic tasks without a specific spacing
interval will now run on the default interval which may be less
often than some tasks run now, but with this change they will run
on a more consistent interval.
Closes-Bug: #1319232
Related-Bug: #1276203
Related-Bug: #1272830
Change-Id: I4dd20f68175165