[SERVER-40168] Pull the OplogTruncaterThread out of WiredTigerKVEngine and put it above the storage layer Created: 15/Mar/19 Updated: 10/Oct/19 Resolved: 11/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Gabriel Villasana (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Execution Team 2019-06-17, Execution Team 2019-07-01, Execution Team 2019-07-15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The OplogTruncaterThread will still call into the storage engine, but it's logic does not need to exist in that layer. Replication should control
Currently starting the OplogTruncaterThread is a byproduct of creating a local.oplog.* collection record store. That special logic can go away. The WiredTigerKVRecordStore currently depends on the OplogTruncaterThread to initialize the OplogStones logic, which then pivots from the regular capped collection clean up process to the OplogStones variation. The storage layer will need some other indicator – ideally a generic one – to signal use of the OplogStones. |
| Comments |
| Comment by Githook User [ 10/Oct/19 ] |
|
Author: {'name': 'Maria van Keulen', 'username': 'mvankeulen94', 'email': 'maria.vankeulen@mongodb.com'}Message: (cherry picked from commit 294a8f68615710b47936d5ee42439d01538ac746)
(cherry picked from commit b35dd89515473c97a87b3c06897e8a7ab51c93cc) This backport was not a straightforward cherry-pick due to |
| Comment by Githook User [ 11/Jul/19 ] |
|
Author: {'name': 'Gabe Villasana', 'username': 'villagab4', 'email': 'villagab4@gmail.com'}Message: |
| Comment by Githook User [ 11/Jul/19 ] |
|
Author: {'name': 'Gabe Villasana', 'username': 'villagab4', 'email': 'villagab4@gmail.com'}Message: |