Merge lp://staging/~brian-murray/daisy/remove-sandbox-dir-after-retrace into lp://staging/daisy
Proposed by
Brian Murray
Status: | Merged |
---|---|
Merge reported by: | Brian Murray |
Merged at revision: | not available |
Proposed branch: | lp://staging/~brian-murray/daisy/remove-sandbox-dir-after-retrace |
Merge into: | lp://staging/daisy |
Diff against target: |
15 lines (+5/-0) 1 file modified
daisy/retracer.py (+5/-0) |
To merge this branch: | bzr merge lp://staging/~brian-murray/daisy/remove-sandbox-dir-after-retrace |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Evan (community) | Approve | ||
Review via email: mp+212187@code.staging.launchpad.net |
Description of the change
This will help reduce the amount of storage that the retracer processes require by cleaning up the sandbox dir in $release-
To post a comment you must log in.
This was originally done for efficiency, if memory serves. In fact, leaving off the --sandbox-dir option would give you much the same effect in a cleaner way.
Could we not instead have a process watching the disk usage on the retracer? When it gets to a charm-defined percentage limit, this process could send SIGINT to the retracer process, which could be taught to finish up the current retrace and then terminate. The watchdog process would then clean up the retracer cache dirs and restart the retracer.
Alternatively, you could have the retracer do the cleanup on behalf of the watchdog, or just flat out kill the retracer process and put our ability to deal with retracers that die mid-retrace to the test. :)
It *should* throw the work back on the queue, since we didn't ack the message in that case, but I've never thoroughly tested it.