[SERVER-29753] create new oplogvisibilitymanager Created: 20/Jun/17 Updated: 30/Oct/23 Resolved: 22/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.13 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage 2017-07-31, Storage 2017-08-21, Storage 2017-09-11 |
| Participants: |
| Description |
|
Currently for WiredTiger, some of the oplog visibility logic is contained in WiredTigerSessionCache. This task is to move that logic, and some logic from WiredTigerRecordStore that is only active for the oplog record store, into a new object. This new object will have one instance per WiredTigerKVEngine, and will be accessible via the recovery unit. |
| Comments |
| Comment by Eric Milkie [ 22/Aug/17 ] |
|
Fixed with 77dc6917428ffad4b9ff2d54d78fa9b225f78a4b |