[Bug 1615482] Re: apt-daily timer runs at random hours of the day
Julian Andres Klode
jak at jak-linux.org
Tue Apr 25 06:42:51 UTC 2017
Of course the load will be higher and peakish again, but the period is
twice as long as it was before (it's now 1 hour instead of 30 minutes),
so that should help.
I don't really get the cloud argument, though. APT will run updates on
boot if the instance was running more than 24 hours ago. And really, are
you saying people are starting cloud instances en masse between 6 and 7?
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1615482
Title:
apt-daily timer runs at random hours of the day
Status in apt package in Ubuntu:
Fix Committed
Bug description:
apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
systemd timer instead of a cron.daily job. This is a good thing,
decoupling apt daily runs from the rest of cron, and ensuring other
cron.daily jobs are not blocked by up to half an hour by the default
settings of unattended-upgrades.
However the policy chosen is to have the apt daily script run at a
random hour of the day in a wrong headed attempt to reduce server
load. This has the side effect of running unattended-upgrades at
random hours of the day — such as business hours — rather than being
confined to between 6:25am and 6:55am, using the defaults.
A better policy would be to have the script activate at 6:00am plus an
interval of 20 minutes at one second intervals reducing the impact of
timezone population spikes, while still allowing unattended-upgrades
to run within a predictable interval, before 7am.
At the very least, some sort of note in the NEWS file detailing the
new behaviour would be welcome.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+subscriptions
More information about the foundations-bugs
mailing list