Compact collection from UI
Compacting of a collection directly from the MongoDB Atlas website UI.
No need to run CLI commands and changing primary database.
Making regular maintenance easier.
-
Yiru commented
Could we have an auto-compact option during the maintenance window, and that would be a lot better
-
Shashank commented
Because of this, we have been facing 3 problems-
1. Cost (~$80-$100 extra)
2. Backup restore takes time because of weird comparison of disk space between source and target
3. Running compact command is not easy. -
Matthias commented
I would also recommend to implement this feature. It would be easier to compact a collection when we would be able to execute it via UI
-
Justinas commented
this feature is definitely required! I vote for this feature to be implemented asap
-
Alberto commented
Hi there
MongoDB Atlas is a great service that offers out of the box a lot of cluster management command that will be otherwise tricky to perform without a great knowledge of mongodb.
Something that lacks in my opinion is related to disk management and especially when it comes to reclaim free space.
In my experience occured that for this scenarios:* Usage of online archive functionality to move huge amount of data
* Changes in the behavior of the application that relies on the cluster
* Or a bug in the applicationSome collections (or the oplog) are left with a huge amount of free storage size that will be never used in the future: in this scenario only by manually performing the compact command it is possible to reclaim the free space, that should be used carefully in a production cluster.
__In conclusion, in my opinion, it will be great te be able to perform the compact command on a collection by directly using MongoDB atlas (from the UI or automated mechanism)__
-
Avinash commented
Love the mongo managed service, but this has become a major pain point for us when trying to recover space.
It's a bit tedious to run on every collection, then switch DB's, Change primary so that we can run the same thing again on the third node, etc.
Making this simple via UI will save a lot of effort.