[SERVER-42043] Move the OplogCapMaintainerThread off of BackgroundJob Created: 02/Jul/19  Updated: 02/Feb/24

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

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Daotang Yang
Resolution: Unresolved 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
Assigned Teams:
Storage Execution
Sprint: Execution Team 2023-11-27, Execution Team 2024-01-08, Execution Team 2024-01-22, Execution Team 2024-02-05, Execution Team 2024-02-19
Participants:

 Description   

OplogTruncaterThread is started and then never shut down. The thread is just left running. We should clean it up properly with shutdown() functionality.

We wish to move functionality off of the BackgroundJob class so that we can eventually delete the BackgroundJob class.



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

We still need to figure out what component should own this, once we have startup and shutdown logic. SERVER-40168 will move the initialization code up to the repl StorageInterface layer, but that class neither own things nor has startup/shutdown code – it's just a helper/wrapper interface to facilitate repl operations against the storage layer.

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