https://nanmu.me/en/tags/wiredtiger/Recent content in WiredTiger on nanmu42Hugo -- gohugo.ioeni@nanmu.me (nanmu42)i@nanmu.me (nanmu42)Copyright ©{year} LI ZhennanSun, 31 May 2020 10:48:05 +0800weeklyweeklyhttps://nanmu.me/en/posts/2020/a-practical-guide-to-reclaim-disk-space-from-mongo-db/Sun, 31 May 2020 10:48:05 +0800i@nanmu.me (nanmu42)Tue, 06 Aug 2024 10:39:07 +0800https://nanmu.me/en/posts/2020/a-practical-guide-to-reclaim-disk-space-from-mongo-db/Dedicated to Ops who are weighed down with worry about high-disk usage of MongoDB. This post applies to MongoDB 3.2 or better and all following operations run on Mongo Shell. You need to confirm your Mongo’s engine is WiredTiger: 1 2 db.serverStatus().storageEngine // expect output: { "name" : "wiredTiger" } Where to start Find the main concern, use show dbs to locate the biggest databases, and then locate the biggest collections after use your_biggest_db:nanmu42MongoDBWiredTigerNotes and Discussions