[SERVER-41381] Expire oplog entries by time instead of as a capped collection Created: 30/May/19 Updated: 16/Mar/22 Resolved: 15/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | hiller1 | Assignee: | Louis Williams |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Execution Team 2021-11-29 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Mongodb oplog design flaw Why can't you define the expiration time as the MySQL binlog, instead of the MongoDB oplog overwrite solution? |
| Comments |
| Comment by Louis Williams [ 15/Nov/21 ] |
|
This is a duplicate and was completed by See the documentation for oplogMinRetentionHours here. |
| Comment by Evin Roesle [ 18/Feb/20 ] |
|
We are closing this ticket as there is a larger project being planned that will allow a user to cap oplog by time in addition to size. I will comment on this ticket when that project is completed. |
| Comment by Danny Hatcher (Inactive) [ 22/Aug/19 ] |
|
Thank you for your report. We are looking into the feasibility of making such a change. |