Define a better policy for disabling archive mirrors
Bug #80990 reported by
Guilherme Salgado
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Archive mirrors are currently disabled by the mirror prober only if no content at all is found on them. This is not optimal because we end up including outdated mirrors in the public listings.
After some discussion we agreed to do the following. For now, at least.
1. If there's anything 4 days behind on an archive mirror, that mirror should be disabled.
2. If any files are missing from any released (current and supported) releases on the RELEASE pocket, the mirror should be disabled.
description: | updated |
Changed in launchpad: | |
milestone: | 1.1.12 → none |
Changed in launchpad: | |
milestone: | none → 1.1.12 |
Changed in launchpad: | |
milestone: | 1.1.12 → 1.2.1 |
Changed in launchpad: | |
assignee: | salgado → carlos |
Changed in launchpad: | |
milestone: | 1.2.1 → 1.2.2 |
Changed in launchpad: | |
milestone: | 1.2.2 → none |
affects: | launchpad-foundations → launchpad-registry |
Changed in launchpad-registry: | |
importance: | Medium → Low |
tags: | added: mirror |
To post a comment you must log in.
One thing we could easily do is disable all mirrors with an overall freshness "worse" than N days. That'd be trivial and could be a starting point, at least.