scan_branches terminated for excessive memory abuse
Bug #690021 reported by
Steve McInerney
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Unassigned |
Bug Description
bzrsyncd 20 0 5681m 4.5g 2432 D 1 57.0 4:19.95 /usr/bin/python /srv/bzrsyncd.
4.5Gb RSS, 5Gb Virt.
terminated, as that was driving us into swap.
https:/
This was while scanning ~vcs-imports/
Related branches
lp:~mbp/launchpad/690021-rlimit
- Robert Collins (community): Approve
- Martin Pool (community): Disapprove
- Tim Penhey (community): Needs Information
- Michael Hudson-Doyle: Approve
-
Diff: 21 lines (+5/-0)1 file modifiedcronscripts/scan_branches.py (+5/-0)
tags: | added: canonical-losa-lp |
description: | updated |
Changed in launchpad: | |
status: | Fix Committed → Triaged |
tags: | removed: qa-untestable |
Changed in launchpad: | |
assignee: | Martin Pool (mbp) → nobody |
To post a comment you must log in.
On 14 December 2010 16:07, Steve McInerney launchpad. net/production/ launchpad/ cronscripts/ scan_branches. py
<email address hidden> wrote:
> Public bug reported:
>
> bzrsyncd 20 0 5681m 4.5g 2432 D 1 57.0 4:19.95 /usr/bin/python
> /srv/bzrsyncd.
>
> 4.5Gb RSS, 5Gb Virt.
> terminated, as that was driving us into swap.
Perhaps, rather than relying on it being manually terminated, we
should set a ulimit on it so that it's consistent and doesn't harm
anything else?
If we wanted to make such a change, by what technical means could we
do so (is there a branch that controls how it's run?) and who ought to
be involved in authorizing it?
--
Martin