juju remove-backup should release space to the filesystem
Bug #1743986 reported by
Junien Fridrick
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Hi,
juju backups are stored in mongodb, and can be pretty big. I removed 30GB worth of backups from a 2.2.6 controller yesterday (that was 3 backups), and the space was not released to the filesystem.
It may be worth compacting the collections in the "backups" database after removing a backup. The documentation [1] states that "compact only blocks operations for the database it is currently operating on.", so it should not block the rest of the operations.
Thanks
[1] https:/
tags: | added: backup-restore |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in juju: | |
assignee: | nobody → Heather Lanigan (hmlanigan) |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Triaged |
assignee: | Heather Lanigan (hmlanigan) → nobody |
To post a comment you must log in.
My gut says that there is probably a difference in Mongo 2.4 vs 3.2 and
what we could do. I believe 2.4 only supports "repairDatabase" to squish
everything, vs "compact" which can target specific collections.
I suppose in either case, backups should already be isolated in its own
database.
Going a little bit further, though. There is some concern if you were
removing lots of backups. We wouldn't really want to compact between each
removal. (I have 30, delete one, compact 29GB, delete another, compact
28GB, delete another, 27GB... etc.)
"juju remove-backup" doesn't yet support multiple backups to be removed. I
think it should.
I also wonder if it should take an optional flag about compacting the
database. (We could default it to compact and just allow you to specify
--no-compact, potentially)
We discussed in Cape Town the possibility of limits on the backup table,
akin to our other limits. (limit total number of preserved backups, total
size, etc, and having the automatically expire).
I could live with only changing it to auto compact on delete, since the
user intent is almost always to return disk space to the OS, not back to
Mongo. But I would like us to make that reasonably efficient in bulk.
On Thu, Jan 18, 2018 at 4:38 PM, Heather Lanigan <<email address hidden>
> wrote:
> ** Tags added: backup-restore /bugs.launchpad .net/bugs/ 1743986 /bugs.launchpad .net/juju/ +bug/1743986/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> juju remove-backup should release space to the filesystem
>
> To manage notifications about this bug go to:
> https:/
>