juju create-backup: Failed: oplog overflow: mongodump was unable to capture all new oplog entries during execution;
Bug #1790875 reported by
Felipe Reyes
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
when running juju create-backup in a fairly big database the following error was raised:
Failed: oplog overflow: mongodump was unable to capture all new oplog entries during execution;
This happens when mongodump is being generated from a SECONDARY replica set, more details at https:/
So juju should always connect to the PRIMARY when generating a mongodump.
| tags: | added: 4010 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.5-beta1 |
| Changed in juju: | |
| milestone: | 2.5-beta1 → 2.5-beta2 |
| Changed in juju: | |
| milestone: | 2.5-beta2 → 2.5.1 |
Revision history for this message
| Paul Collins (pjdc) wrote | #1 |
| tags: | removed: 4010 |
Revision history for this message
| Felipe Reyes (freyes) wrote Re: [Bug 1790875] Re: juju create-backup: Failed: oplog overflow: mongodump was unable to capture all new oplog entries during execution; | #2 |
Revision history for this message
| Felipe Reyes (freyes) wrote | #3 |
| Changed in juju: | |
| milestone: | 2.5.1 → 2.5.2 |
| Changed in juju: | |
| milestone: | 2.5.2 → 2.5.3 |
| Changed in juju: | |
| milestone: | 2.5.3 → 2.5.4 |
| Changed in juju: | |
| milestone: | 2.5.4 → 2.5.5 |
| Changed in juju: | |
| milestone: | 2.5.6 → 2.5.8 |
| Changed in juju: | |
| milestone: | 2.5.8 → 2.5.9 |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #4 |
| Changed in juju: | |
| milestone: | 2.5.9 → none |
| tags: | added: backup-restore |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #5 |
| Changed in juju: | |
| importance: | High → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
I ran into this consistently on a JAAS controller we were preparing to upgrade to 2.4.7, apparently always while backing up statueshistory. So perhaps it's also a function of busyness as well as or instead of size?