[SERVER-46094] Use wall instead of ts field for oplog retention policy Created: 12/Feb/20 Updated: 29/Oct/23 Resolved: 28/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Andrew Chen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2020-02-24, Execution Team 2020-03-09 |
| Participants: |
| Description |
|
As outcome of the scope / design discussion for this project, we decided to do the extra work to use the wall field instead of the ts field to calculate the age of oplog entries for retention purposes. This requires a new wall member in the OplogStones::Stone struct, as well as code to set it properly during oplog scanning/sampling at startup as well as steady state oplog stone creation. |
| Comments |
| Comment by Githook User [ 28/Feb/20 ] |
|
Author: {'name': 'Andrew Chen', 'email': 'andrew.chen@10gen.com'}Message: |