don't aggravate mongo by changing its oplog size once its already been started
Bug #1749350 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
| 2.3 |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Right now, if you successfully bootstrap juju and have everything working. Its possible that just normal usage of the system will decrease the free disk space.
On restart, because we dynamically determine what oplog size to use, it may change its mind.
Given it already has the data allocated, we can just use the data we have (we don't truncate the files anyway).
| Changed in juju: | |
| milestone: | none → 2.3.3 |
| Changed in juju: | |
| milestone: | 2.3.3 → none |
| Changed in juju: | |
| status: | In Progress → Triaged |
| importance: | High → Medium |
| assignee: | John A Meinel (jameinel) → nobody |
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
The original issue was determined to not be caused by this, and the code in question is layered in such a way to make it very difficult to change this behavior. Users who might be affected by this can set the oplog size to their desired size directly in agent.conf with MONGO_OPLOG_SIZE.
Unfortunately, we don't seem to expose this as ControllerConfig, so admins can't set it at bootstrap or controller it from the juju client.