[SERVER-5966] Request for option to specify oplog size in seconds Created: 30/May/12  Updated: 30/May/19  Resolved: 02/Apr/13

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

Type: Improvement Priority: Minor - P4
Reporter: Shawn O'Rourke Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: oplog, replication
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-9036 Request for option to specify oplog s... Closed
Duplicate
is duplicated by SERVER-41381 Expire oplog entries by time instead ... Closed
Participants:

 Description   

I would like to submit a request for an option to specify the replica set oplog size in seconds. I currently only see the option to specify the oplog size in MB. The benefit here is that a replica set could have an oplog collection that goes back X hours, days, etc. and calculating this wouldn't require analyzing the activity on the database.

I can provide more detail if needed. Thank you.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 02/Apr/13 ]

This could theoretically be done with TTL, but the choice of size was very explicit.

It is very fast and efficient, as well as doesn't suffer from sudden write spikes.

With time, if you get a write spike, you could run out of disk space, which for an oplog would be very bad.

Generated at Thu Feb 08 03:10:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.