[SERVER-37975] Remove _oplogMaxAtStartup in WiredTigerOplogManager Created: 06/Nov/18 Updated: 29/Oct/23 Resolved: 09/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Xiangyu Yao (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage NYC 2018-11-19 |
| Participants: |
| Description |
|
We no longer need _oplogMaxAtStartup as the lower bound for visibility timestamp because we explicitly set oplogReadTimestamp to be the same value as _oplogMaxAtStartup on startup and it will only grow beyond that value. Code and comments related to this variable can be removed. |
| Comments |
| Comment by Githook User [ 08/Nov/18 ] |
|
Author: {'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}Message: |