mongo memory profile setting needs to be configurable
Bug #1673314 reported by
Anastasia
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
From bug # 1671466, we have the ability to customise memory profile setting for mongo. However, we do not expose this to the user.
We should :D
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Fix Committed |
| milestone: | none → 2.2-beta1 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
It looks like we have exposed this configuration to the user but our documentation should also reflect that. It was very hard to find:
Bootstrap with --config=
This is a controller config which can be changed from the command line but the change might not immediately take effect.
Valid values are "low" (most conservative mongo memory profile) and "default" (mongo memory profile shipped by default with mongo).
Doc issue: https:/