[SERVER-48181] Incorrect destruction order of Cache vs ThreadPool in the ReadThroughCache unit-tests Created: 13/May/20  Updated: 29/Oct/23  Resolved: 25/May/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.4.0-rc5
Fix Version/s: 4.4.0-rc7, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: neweng, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-46154 Make ReadThroughCache be driven by a ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Execution Team 2020-06-01
Participants:
Linked BF Score: 0

 Description   

Some of the ReadThroughCache unit-tests first create the ThreadPool, then the Cache for testing.

This order contradicts the contract of ReadThroughCache.

As part of this ticket we should see if there is some generic pattern that can be used for these unit-tests (e.g., this) in order to ensure they all comply instead of fixing them one by one.



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

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-48181 join threads in ReadThroughCacheAsyncTest before destroying cache

(cherry picked from commit 7e095f938a240ca92877820d21329bd52ee57382)
Branch: v4.4
https://github.com/mongodb/mongo/commit/5ecf380910f427e079617ffb0aa4dba1a6e388b4

Comment by Githook User [ 25/May/20 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-48181 join threads in ReadThroughCacheAsyncTest before destroying cache
Branch: master
https://github.com/mongodb/mongo/commit/7e095f938a240ca92877820d21329bd52ee57382

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