[SERVER-42374] TimestampMonitor should stop its PeriodicJob prior to destructing itself Created: 24/Jul/19  Updated: 29/Oct/23  Resolved: 24/Jul/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.2.0-rc5, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-48384 Make PeriodicJob stop before Timestam... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2019-07-29
Participants:
Linked BF Score: 58

 Description   

When the TimestampMonitor is shutting down, we should also stop its periodic job prior to destructing the TimestampMonitor object. The periodic job uses member variables of the TimestampMonitor which would be freed after its destruction.



 Comments   
Comment by Githook User [ 24/Jul/19 ]

Author:

{'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-42374 TimestampMonitor should stop its PeriodicJob prior to destructing itself
Branch: v4.2
https://github.com/mongodb/mongo/commit/ca30a67fa011e73e582c43ac88000fed4512a793

Comment by Githook User [ 24/Jul/19 ]

Author:

{'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-42374 TimestampMonitor should stop its PeriodicJob prior to destructing itself
Branch: master
https://github.com/mongodb/mongo/commit/f38eabe384361ca989df73526971a30fe40ffca5

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