[SERVER-52515] Remove PeriodicTask Created: 30/Oct/20  Updated: 23/Feb/23  Resolved: 18/Mar/22

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

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Backlog - Service Architecture
Resolution: Won't Do Votes: 0
Labels: ben-sa-triage, re-triaged-ticket
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-52514 Make the legacy connection pool a Ser... Closed
depends on SERVER-52516 Make LockManager a ServiceContext dec... Closed
Related
Assigned Teams:
Service Arch
Participants:

 Description   

PeriodicTask (here) is used with DBConnectionPool and LockManager. We never call stopRunningPeriodicTasks(). We should remove it in favor of use of PeriodicRunner which provides the same features with better lifetime guarantees and flexibility.



 Comments   
Comment by Blake Oler [ 26/Jan/23 ]

Keeping this closed.

Comment by Lauren Lewis (Inactive) [ 18/Mar/22 ]

We haven’t heard back from you for some time, so we're going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:28:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.