[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:
Duplicate
duplicates SERVER-38296 convert OplogTruncaterThread to be ma... Closed
Related
is related to SERVER-40173 Create a formal storage interface for... Backlog
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

  • whether to start the thread
  • when to start the thread

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: SERVER-43322 Add tunable oplog stone sizes and track truncation speeds

(cherry picked from commit 294a8f68615710b47936d5ee42439d01538ac746)

SERVER-43322 Disallow oplog_sampling.js on inMemory storage enigne

(cherry picked from commit b35dd89515473c97a87b3c06897e8a7ab51c93cc)

This backport was not a straightforward cherry-pick due to SERVER-40168
existing in master and not v4.2.
Branch: v4.2
https://github.com/mongodb/mongo/commit/dd819eb95636f47f13638259208ae8a69e48ded7

Comment by Githook User [ 11/Jul/19 ]

Author:

{'name': 'Gabe Villasana', 'username': 'villagab4', 'email': 'villagab4@gmail.com'}

Message: SERVER-40168 Pull the OplogTruncaterThread out of WiredTigerKVEngine and put it above the storage layer
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/702f9f21105675bc23e26d80e719a55206601913

Comment by Githook User [ 11/Jul/19 ]

Author:

{'name': 'Gabe Villasana', 'username': 'villagab4', 'email': 'villagab4@gmail.com'}

Message: SERVER-40168 Pull the OplogTruncaterThread out of WiredTigerKVEngine and put it above the storage layer
Branch: master
https://github.com/mongodb/mongo/commit/d9b6940984db00c428441139a33f19b207e35f30

Generated at Thu Feb 08 04:54:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.