(1) We have the following cluster, with 100 GB of storage, per the image above.

. .

(2) On our cluster's overview page, it shows we are using 43.3 GB out of a 100 GB max. Given that our config has 100 GB of storage, I want to assume that the 100 GB of disc space is the same as the 100 GB of available storage?

. .

(3) However, when I click into our database, it shows the DB size is 66.64 GB 3.21 GB of indexes, for a total size of roughly 70GB.

Question: what is the difference between the 100GB of available storage / disc, and the database size index size of 70GB? Should we be concerned that the 70 GB is approaching 100GB, or is it only the 43.3 GB of disc usage that matters?

CodePudding user response：

Your mongodb database is using by default wiredTiger storage engine with snappy compression which mean that most probably your data stored on disk is using 43.3GB , but the actual(uncompressed) data size is ~ 70GB , so there is no place to worry about since you have used only 43.3% from your 100GB storage. Afcourse you need to monitor your data grow and if it is increasing faster you may need to allocate more space ...