[SERVER-50175] Fix CatalogCache's threadPool shutdown order Created: 07/Aug/20  Updated: 29/Oct/23  Resolved: 07/Aug/20

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

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-2, thread-sanitizer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-49976 Cleanup database cache on shard removal Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-08-10
Participants:
Linked BF Score: 0

 Description   

The thread pool of the CatalogCache needs to be constructed before the _databaseCache because it requires it. On the other hand to prevent access to already freed memory, the thread pool needs to be shutdown and joined before to destruct the _databaseCache



 Comments   
Comment by Githook User [ 07/Aug/20 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-50175 Fix CatalogCache's threadPool shutdown order
Branch: master
https://github.com/mongodb/mongo/commit/87dff4a7082e5a3c28ebafbb5f344e37abcee940

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