Metadata sync should use a local base copy
Bug #1673110 reported by
David Lawson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Repository Cache Charm |
Won't Fix
|
High
|
Unassigned | ||
| ubuntu-repository-cache (Juju Charms Collection) |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
The metadata.py sync rsyncs the full set of metadata from the archive every time it runs, which seems sub-optimal both in terms of our bandwidth usage, load on archive servers and time to sync. I would suggest that it check for a local, known good copy of the metadata and, if found, copy it to a new location, set the sync target to that copy to get the benefit of only transferring deltas, then when the sync is finished, verify the new location's integrity and update symlinks.
| Changed in ubuntu-repository-cache (Juju Charms Collection): | |
| importance: | Undecided → Wishlist |
| Changed in ubuntu-repository-cache: | |
| importance: | Undecided → Wishlist |
| tags: | added: id-58c98c42c44e5f586ceeb5fc |
Revision history for this message
| Paul Gear (paulgear) wrote | #1 |
| Changed in ubuntu-repository-cache: | |
| importance: | Wishlist → High |
| Changed in ubuntu-repository-cache (Juju Charms Collection): | |
| importance: | Wishlist → High |
Revision history for this message
| Haw Loeung (hloeung) wrote | #2 |
| Changed in ubuntu-repository-cache: | |
| status: | New → Won't Fix |
| Changed in ubuntu-repository-cache (Juju Charms Collection): | |
| status: | New → Won't Fix |
To post a comment you must log in.
This is more than a wishlist concern: Azure bandwidth is expensive, and so is the bandwidth on our archive servers. When metadata sync fails due to another bug, this means that it keeps using bandwidth for files which are already synced.