old/cruft branch cleanup needed wrt importds

Bug #903051 reported by Steve McInerney on 2011-12-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

The server that the importd slaves write to is getting a tad on the full size.
It appears we have all sorts of old, possibly even ancient cruft that could be removed.

12Gb .db files don't help.

To open discussion:
Would be looking for a method - prefer automated, but wouldn't have to be - to be able to go through the various files/directories on the written-to server and remove those files/directories that are no longer relevant.
* perhaps a cron on a sole importd slave that could query and delete as necessary
* a report generated "somewhere" that webops staff could run; if these exist, leave alone; if something isn't in that list, remove.

Steve McInerney (spm) on 2011-12-12
tags: added: canonical-losa-lp
Jelmer Vernooij (jelmer) wrote :

We should no longer be generating .db files on escudero - the code imports now store their caches in a tarball and/or in the cache directory on the individual import slaves.

Is the size of the combined .tar.gz files a problem?

tags: added: code-import
Graham Binns (gmb) on 2011-12-12
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Steve McInerney (spm) wrote :

> Is the size of the combined .tar.gz files a problem?

yes and no. Yes in that they do keep growing; so having some method of cleaning the old no longer valid cruft is useful.
No in that we can always add more disk.

Ideally we want the two somewhat in balance; so we're not just blindly adding disk.

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

Other bug subscribers