excessive mongodb disk usage recovered with a repair/repack

Bug #1674656 reported by Gareth Woolridge
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
juju-core-1 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

IS have a number of bootstrap nodes with small <10GB disks, particularly in AWS where root disk is often only 8GB with our current sizing.

Periodically we get disk space alerts and find that there is little we can clean up on the instance, with juju's mongodb using the vast majority of space.

The environment I specifically dealt with was running 1.25.10

We've been able to free up significant disk space by running a repair/repack of the mongodb:

systemctl stop juju-db # or 'initctl stop juju-db'

/usr/lib/juju/bin/mongod --auth --dbpath /var/lib/juju/db --sslOnNormalPorts --sslPEMKeyFile /var/lib/juju/server.pem --sslPEMKeyPassword xxxxxxx --port 37017 --noprealloc --syslog --smallfiles --nojournal --keyFile /var/lib/juju/shared-secret --replSet juju --ipv6 --oplogSize 512 --repair --repairpath /mnt

Ideally juju would become better at managing and recovering space in it's DB.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in juju-core-1 (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.