MAAS 3.2 deb package memory leak after upgrading
Bug #2012596 reported by
German Mazurenko
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Committed
|
High
|
Seyeong Kim | ||
3.2 |
Fix Released
|
High
|
Seyeong Kim | ||
3.3 |
Fix Released
|
High
|
Seyeong Kim | ||
3.4 |
Fix Released
|
High
|
Unassigned | ||
3.5 |
Fix Released
|
High
|
Unassigned |
Bug Description
I’m using deb package version 3.2.7 with region controller, rack controller and postgres 14 on it’s own 20.04 virtual machine each(before upgrading it was 18.04 and pg 9.5).
After upgrading from 2.8 to 3.2.6(upgrading from 3.2.6 to 3.2.7 made no difference) I noticed that region and rack controllers started uncontrollably increasing their memory usage for ~1GB per day(or slower on my playground with less bare metal and virtual servers), until OOM-killer comes or System Administrator restarts it.
I tried to debug it myself with tracemalloc, pympler, etc but unsuccessfully.
Repo I'm using: http://
Related branches
~seyeongkim/maas:fixing_memory_leak_apt_get_3.2
- Björn Tillenius: Approve
- MAAS Lander: Approve
-
Diff: 38 lines (+17/-3)1 file modifiedsrc/provisioningserver/utils/deb.py (+17/-3)
~seyeongkim/maas:fixing_memory_leak_apt_get_3.3
- Björn Tillenius: Approve
- MAAS Lander: Approve
-
Diff: 38 lines (+17/-3)1 file modifiedsrc/provisioningserver/utils/deb.py (+17/-3)
~troyanov/maas:backport-d792780-3.4
- MAAS Lander: Approve
- Anton Troyanov: Approve
-
Diff: 38 lines (+17/-3)1 file modifiedsrc/provisioningserver/utils/deb.py (+17/-3)
~troyanov/maas:backport-d792780-3.5
- Anton Troyanov: Approve
-
Diff: 38 lines (+17/-3)1 file modifiedsrc/provisioningserver/utils/deb.py (+17/-3)
~seyeongkim/maas:fixing_memory_leak_apt_get
- Björn Tillenius: Approve
- MAAS Lander: Approve
-
Diff: 38 lines (+17/-3)1 file modifiedsrc/provisioningserver/utils/deb.py (+17/-3)
affects: | maas → maas (Ubuntu) |
description: | updated |
no longer affects: | maas |
affects: | maas (Ubuntu) → maas |
Changed in maas: | |
status: | Incomplete → New |
status: | New → Incomplete |
Changed in maas: | |
status: | Incomplete → New |
Changed in maas: | |
status: | Incomplete → New |
status: | New → Incomplete |
Changed in maas: | |
status: | Invalid → New |
Changed in maas: | |
status: | New → Incomplete |
Changed in maas: | |
status: | Incomplete → New |
status: | New → Incomplete |
Changed in maas: | |
status: | Incomplete → New |
status: | New → Incomplete |
tags: | added: bug-council |
tags: | removed: bug-council |
Changed in maas: | |
status: | Incomplete → New |
status: | New → Incomplete |
tags: | added: sts |
Changed in maas: | |
milestone: | none → 2.8.9 |
status: | In Progress → Fix Committed |
Changed in maas: | |
importance: | Undecided → High |
milestone: | 2.8.9 → 3.6.0 |
To post a comment you must log in.
Hi German,
Thats interesting and I don't think I ever noticed the same behaviour.
1. Does this memory leak happens if you make a clean 3.2.6 install? /maas.io/ docs/how- to-review- and-report- bugs#heading- -logfiles
2. If you make a clean 2.8 install and upgrade it to 3.2.6 will it leak?
3. Any noticeable errors in MAAS logs?
https:/
4. What did tracemalloc show? Would be great if you can provide top 10 from tracemalloc /docs.python. org/3/library/ tracemalloc. html#display- the-top- 10
https:/