Comment 3 for bug 1680582

@Peter Sabaini (peter-sabaini),
MgoPurge tool now has a facility to prune transactions, thus greatly reducing db size. Pruning can be run on a live, non-paused system as per wiki. Please test it on non-production environment first - we have mostly developed it for Juju 2.x environments which run on mongo 3.2.

Do you happen to know how many transactions that can be pruned may be in the db currently?

In Juju 2.2, equivalent functionality will be run every 2hrs when/if needed.

If restarting state server works well, mgopurge may not be needed as frequently.

I am marking this bug as Won't Fix since restarting state server is a workaround that helps you to get out of the tight spot and we do not have capacity to focus on Juju 1.25.x at the moment - we are full steam ahead on Juju 2.x.