Poor "juju create-backup" performance
Bug #1680683 reported by
Paul Gear
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
Backing up juju shared controllers with any significant number of models performs very poorly. On a controller with around 40 models [1], "juju create-backup" took 1 hour and 19 minutes to generate and download, and the resultant backup tarball was 6 GB in size.
This is going to be exacerbated with JAAS, and we need to find a way to confidently upgrade controllers without waiting over an hour to get a viable backup. Are there parts of the database which could be legitimately excluded from the backup?
tags: | added: canonical-is |
Changed in juju: | |
status: | New → Incomplete |
To post a comment you must log in.
Do you have numbers on where the time is spent? (And what version the story/etc.
controller is running.) I wonder if you're running into extra data from
some of the collections that aren't being cleaned up. Or whether it is just
that you have lots of large charms or if it is logs/statuseshi
John
=:->
On Apr 7, 2017 8:30 AM, "Paul Gear" <email address hidden> wrote:
> ** Tags added: canonical-is /bugs.launchpad .net/bugs/ 1680683 /bugs.launchpad .net/juju/ +bug/1680683/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> Poor "juju create-backup" performance
>
> To manage notifications about this bug go to:
> https:/
>