<nagios> surf:mozilla-releases rsync size is CRITICAL: mozilla-releases rsync is 119 GB. Ben, looks like you only need firefox/releases/4.0b8/update/ for bug 627598 ? We also might have enough grunt to handle that from dm-download02 once bug 628182 is fixed. I'll go ahead and pull 3.5.15 and 3.6.12 since it's some time since those were superseded by the next release. Note to RelEngers - if you want to revoke a release from the mirrors you have to modify rsyncd-mozilla-prereleases.exclude as well as rsyncd-mozilla-releases.exclude.
It would be great to remove these from the mirrors: thunderbird/releases/126.96.36.199 firefox/releases/3.0.19-real-real Need to track down how many requests we get per day for those though. I suspect it's mostly people stuck in updates loops but no real way to tell. We can disable updates to 188.8.131.52 and drop the occasional person with an old version who would update. More from EOL branches - can they go ? thunderbird/releases/3.0.10 thunderbird/releases/3.0.11 seamonkey/releases/1.1.19 About to become (even more) redundant - can they go ahead of next point release ? thunderbird/releases/3.1.6 seamonkey/releases/2.0.10
(In reply to comment #1) > seamonkey/releases/1.1.19 That one can go, yes, it's been EOL for long enough to do that, and should only need the usual flip of a flag in the SeaMonkey 1.1.19 download web page to not makes us point to releases.m.o > seamonkey/releases/2.0.10 With the rather small amount of downloads the product has overall, we'd even be able to serve full releases from FTP with the capacities we have nowadays. We can easily have the 70-140 downloads per day of SM 2.0.10 go that path (and us flipping the switch on the release archive page). Being a bit more elaborate this time so Callek, who's doing most SM releng now, and InvisibleSmiley, who's getting more familiar with SM website admin, get a grip on what's going on here. :)
(In reply to comment #0) > Ben, looks like you only need firefox/releases/4.0b8/update/ for bug 627598 ? > We also might have enough grunt to handle that from dm-download02 once bug > 628182 is fixed. That's right, should be fine w/out it on the mirrors now.
bug 628185 removed a few other more recent releases out of the -releases module, making dm-download02 the only place to go to get those releases. The addition of those to dm-download02's load was probably just enough to push it over.
er, that comment was meant for bug 628986
(In reply to comment #1) > More from EOL branches - can they go ? > thunderbird/releases/3.0.10 > thunderbird/releases/3.0.11 > > About to become (even more) redundant - can they go ahead of next point release > ? > thunderbird/releases/3.1.6 Ping t'bird people re ^^ I'm going to look at removing all but update/ for Fx 184.108.40.206 and 3.0.19.
(In reply to comment #1) > It would be great to remove these from the mirrors: > thunderbird/releases/220.127.116.11 > firefox/releases/3.0.19-real-real > Need to track down how many requests we get per day for those though. I suspect > it's mostly people stuck in updates loops but no real way to tell. We can > disable updates to 18.104.22.168 and drop the occasional person with an old version > who would update. That's actually just under half of Thunderbird 2.0.0.x users. I've not looked at how the pre .24 numbers have changed over time. However, I guess I probably don't care about dropping updates to .24. If you do, we need to first change our start pages first as they currently tell users that they can do help -> check for updates, and remove a web page from our site (it still offers 2.0.x downloads). (In reply to comment #6) > (In reply to comment #1) > > More from EOL branches - can they go ? > > thunderbird/releases/3.0.10 > > thunderbird/releases/3.0.11 > > > > About to become (even more) redundant - can they go ahead of next point release > > ? > > thunderbird/releases/3.1.6 > > Ping t'bird people re ^^ 3.0.11 was only EOL in December, and we still have people on older versions, so I'd kinda prefer to keep that open for a bit (and again, there's a web page with these on, so we'd need to remove that from the site as well). 3.0.10 can definitely go. 3.1.6 can go as all updates should be pointing to 3.1.7.
Summary of changes Added to rsyncd-mozilla-prereleases.exclude (to sync it up) - firefox/releases/4.0b9 Added to rsyncd-mozilla-prereleases.exclude and rsyncd-mozilla-releases.exclude: - firefox/releases/22.214.171.124/contrib-localized - firefox/releases/126.96.36.199/contrib - firefox/releases/188.8.131.52/linux-i686 - firefox/releases/184.108.40.206/mac - firefox/releases/220.127.116.11/source - firefox/releases/18.104.22.168/update/linux-i686 - firefox/releases/22.214.171.124/update/mac - firefox/releases/126.96.36.199/win32 - firefox/releases/3.0.19-real-real/contrib-localized - firefox/releases/3.0.19-real-real/contrib - firefox/releases/3.0.19-real-real/linux-i686 - firefox/releases/3.0.19-real-real/mac - firefox/releases/3.0.19-real-real/source - firefox/releases/3.0.19-real-real/update/linux-i686 - firefox/releases/3.0.19-real-real/update/mac - firefox/releases/3.0.19-real-real/win32 - firefox/releases/4.0b10 - seamonkey/releases/1.1.19 - seamonkey/releases/2.0.10 - thunderbird/releases/3.0.10 - thunderbird/releases/3.1.6 I'll verify we have CheckNow set to True for these, and turn it off in a few days. Seamonkey people, please make your webpage changes.
Added to rsyncd-mozilla-prereleases.exclude and rsyncd-mozilla-releases.exclude: - thunderbird/releases/188.8.131.52/contrib-localized - thunderbird/releases/184.108.40.206/contrib - thunderbird/releases/220.127.116.11/linux-i686 - thunderbird/releases/18.104.22.168/mac - thunderbird/releases/22.214.171.124/source - thunderbird/releases/126.96.36.199/update/linux-i686 - thunderbird/releases/188.8.131.52/update/mac - thunderbird/releases/184.108.40.206/win32 Also fixed rsyncd-mozilla-current.exclude to include thunderbird/releases/3.1.7 rather than 3.1.3.
NB the strategy for fx 220.127.116.11 & 3.0.19, and thunderbird 18.104.22.168, is that most of the downloads we still see for those are for windows update files. So everything else is excluded from the mirrors.
Down to 80G now, and expect about 32G of new files when the next round of releases come along, so a little more would be good. Bug 626564 to try to trim down the 9.8G of addons/, and bug 635132 for the 14G in mobile/.
Good enough for now, given the mobile bug is making progress.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.