I’m running a 3 node cluster with v5.0.8.
The parameter oplogMinRetentionHours on primary is set to 12 hours, but oplog length is over 20 hours. How can I ‘wake up’ Mongo to shrink it back to 12 hours?
There is no problem with majority commit. Write commit is set to 1.
The oplog is much larger than the main collection. 99% of the database is this main collection.
Skip to main content
New & Unread Topics
Topic | Replies | Views | Activity |
---|---|---|---|
Is there any way of getting the server IP from which db call is happening | 1 | 566 | May 2024 |
Set time for Rotate Log Files without crontab | 0 | 246 | Jul 2024 |
Mongosync Large Collection stuck | 0 | 42 | Oct 2024 |
Issue with MongoDB Pods Not Starting After Upgrade Attempt | 1 | 59 | Nov 2024 |
Microk8s Kubernetes and connecting by Service Name | 0 | 55 | Nov 2024 |