Daily 'apt-get update' slowness when using ec2 mirror us-east-1.ec2.archive.ubuntu.com

Bug #1561173 reported by Bill Agee
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu
Confirmed
Undecided
Unassigned

Bug Description

For the last week or so, I've been experiencing a nightly ~1-hour span of time (starting around 11:30 PM PDT), where 'apt-get update' hangs for as long as 30 minutes on systems configured to use the Canonical ec2 mirror in us-east-1:

http://us-east-1.ec2.archive.ubuntu.com/ubuntu/

While that behavior is occurring, the same slow response time seems to exist both for requests from EC2 instances and also from non-Amazon hosts (my home Inet connection, at least).

Navigating the mirror from a web browser becomes noticeably slow in addition to the impact on apt-get.

It looks like similar behavior has occurred with other ec2 mirrors in the past; one suggestion I noticed (http://www.thomasvjames.com/2015/03/ubuntu-apt-slow/) involves forcing the use of an S3-backed apt mirror by appending .s3.amazonaws.com to the repo URL.

However, while the bucket at http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com seems to exist, I get 403 Forbidden errors if I attempt to use that URL in my sources.list and re-run 'apt-get update'.

Someone pointed me to this announcement from 2012 that all ec2 repos were now s3-hosted by default; does that mean that using the .s3.amazonaws.com URLs is moot? Or was the change to use s3 to host us-east-1.ec2.archive.ubuntu.com rolled back at some point?

https://lists.ubuntu.com/archives/ubuntu-cloud-announce/2012-July/000029.html

Thanks!

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1561173/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Haw Loeung (hloeung) wrote :

LP: #1554848 is to fix unattended-upgrades to randomise over a longer period of time.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.