[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: |
|
||||||||||||||||
| 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. |