[SERVER-45552] Mongo oplog Created: 14/Jan/20  Updated: 15/Jan/20  Resolved: 15/Jan/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: 03shady . Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Hello,

 

We are running mongodb replica set.

I have a question about oplog's size , by default it's 5% of the disk size .

What happens when oplog size is full ? Will overwrite old data ? 

I'm asking because of point-in-time recovery backup . 

 

For example i would have oplog backup for 2 weeks retention  , so i dont want to have oplog file from december 2019 ,but only from 1st january 2020 .  What should be done in this case ? 

 

 



 Comments   
Comment by Carl Champain (Inactive) [ 15/Jan/20 ]

Hi shady03@gmail.com,

Our documentation mentions that:

The oplog (operations log) is a special capped collection that keeps a rolling record of all operations that modify the data stored in your databases.

And here is the definition of a capped collection:

A fixed-sized collection that automatically overwrites its oldest entries when it reaches its maximum size.

That said, the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag.

Thank you,
Carl

Generated at Thu Feb 08 05:09:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.