I seem to be having an issue with the oplog.rs@local collection causing a huge size expansion resulting in significant costs. I can run db.stats() to confirm this. It will not release the data back and I cannot seem to find a way to do it myself via compact() (permissions issues), scaling down or testing resilience. I have tried to create roles via the atlas UI and the atlas CLI to no avail. I cannot access the local db which I presume is by design? Am I correct in assuming I need to engage premium support to be able to resolve this?
Skip to main content
This can only be done on M10+ clusters and for system collections (oplog being one) extra permissions are required.
https://www.mongodb.com/docs/manual/reference/command/compact/#compact-required-privileges
See Deleted sizeable content from database, back ups and DB did not shrink - #2 by chris for how to execute a compact correctly in MonogDB Atlas.
New & Unread Topics
Topic | Replies | Views | Activity |
---|---|---|---|
I am unable to make the regex insensitive | 8 | 405 | Jul 2024 |
Best Practices for BulkWrite Performance with Large Documents and Array Fields in a 2-Node Replica Set | 1 | 534 | Sep 2024 |
Mongodb Aggregagion | 1 | 33 | Oct 2024 |
MongoDB v8 regression - server not throwing on invalid database name | 0 | 62 | Dec 2024 |
Using MongoDB locally | 1 | 35 | Feb 25 |