Comment 12 for bug 1655169
Revision history for this message
| Chad Smith (chad.smith) wrote Re: Juju 2.1beta4: Mongo Out Of Memory on bootstrap machine 0 | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I'm not certain if juju has the ability to cap mongo's (or wiredTiger's) memory growth, or whether juju can govern smaller set sizes in memory so mongo doesn't keep around as much data.
It seems this problem is exacerbated by two conditions:
1. having multiple active lxcs on the bootstrap machine
2. having an HA OpenStack deployment (with high-frequency leader election logging)
Background on landscape using the bootstrap machine for deployment is to avoid burning a full machine for just juju's controller when the controller's only role is to support a single region.
If landscape had a config setting knob in juju to tune down the mongo memory caps, then landscape could knowingly set a cap during bootstrap and/or lxc placement events. Landscape would know that the additional lxcs will impact available memory on the bootstrap node so it could limit mongo(wireTiger) growth appropriately.