[SERVER-38296] convert OplogTruncaterThread to be managed by WiredTigerKVEngine Created: 28/Nov/18  Updated: 06/Dec/22  Resolved: 02/Jul/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Backlog - Storage Execution Team
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-40168 Pull the OplogTruncaterThread out of ... Closed
is duplicated by SERVER-42043 Move the OplogCapMaintainerThread off... Backlog
Assigned Teams:
Storage Execution
Participants:

 Description   

Currently OplogTruncaterThread runs free and is never shut down. It should instead be managed properly like WiredTigerKVEngine::WiredTigerCheckpointThread.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 02/Jul/19 ]

Closing this as a duplicate. SERVER-40168 is pulling the thread ownership up out of the WT layer to make it run for any storage engine supporting oplog stones. SERVER-42043 was just filed to move the class off of the BackgroundJob and add actual thread shutdown logic.

Comment by Divjot Arora (Inactive) [ 19/Feb/19 ]

A link to the relevant branch on my fork: https://github.com/divjotarora/mongo/tree/server38296

Comment by Eric Milkie [ 19/Feb/19 ]

This turned out to be a lot more difficult than it seemed. @divjot please post your CR progress here and then we'll put this back on the backlog for later.

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