© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
This does not occur to the same degree on ocata, as multi-worker support[1] was added during the pike development cycle. In ocata, conductor services running on multiple hosts will still all run the same periodic update jobs, which seems inefficient, but not nearly as bad as having multiple workers running periodic updates.
A simple solution that would at least revert to the ocata behaviour would be to only execute periodic updates in the parent process, and not the workers.
[1] https:/