[SERVER-48384] Make PeriodicJob stop before TimestampMonitor destroy its members Created: 21/May/20  Updated: 29/Oct/23  Resolved: 29/May/20

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

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

Issue Links:
Depends
Related
is related to SERVER-42374 TimestampMonitor should stop its Peri... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-06-15
Participants:
Linked BF Score: 25

 Description   

The issue is fixed for versions after v4.2 by SERVER-42374. We should apply the same reordering to v4.2 to prevent the periodic runner from addressing TimestampMonitor members after their destruction.



 Comments   
Comment by Githook User [ 29/May/20 ]

Author:

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

Message: SERVER-48384 Make PeriodicJob stop before TimestampMonitor destroy its members
Branch: v4.2
https://github.com/mongodb/mongo/commit/fa72353e2da4f9f5c7c61d042deb2e9d7a1bcf05

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