Using bridges defined by MAAS 2.1 makes Juju and Mongo eat lots of CPU and RAM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Andrew McDermott |
Bug Description
In MAAS 2.1 you can now define bridged interfaces.
If you bootstrap Juju against a machine configured with bridges juju repeatedly logs an error:
{github.
The worker dies and restarts:
2016-11-24 21:34:51 TRACE juju.worker.
2016-11-24 21:34:51 TRACE juju.worker.
and the process repeats causing Juju and Mongo to use a lot of CPU, and for mongo lots of RAM (>1GB).
This is because the MAAS provider does not cater for the "bridge" type.
Changed in juju: | |
importance: | Undecided → Critical |
assignee: | nobody → Andrew McDermott (frobware) |
summary: |
- Using bridges on MAAS 2.1 makes Juju and Mongo eat lots of CPU and RAM + Using bridges defined by MAAS 2.1 makes Juju and Mongo eat lots of CPU + and RAM |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
milestone: | none → 2.1.0 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
WIP - https:/ /github. com/frobware/ juju/tree/ juju-and- monogo- eats-all- my-ram