[SERVER-50542] Catalog Cache is not cleaned on ShardingTestFixture Created: 26/Aug/20 Updated: 29/Oct/23 Resolved: 27/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: | Marcos José Grillo Ramirez | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1645-Milestone-2, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | 1. Executes a test that extends ShardingTestFixture |
||||||||||||
| Sprint: | Sharding 2020-09-07 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
After the changes on SERVER-49975 a new executor pool is being created within the catalog cache. Additionally the destructor on ShardingTestFixture is not cleaning up the catalog cache previously created on the constructor. If the service context is destroyed and there is a pending refresh, this invariant will be hit on the service context destructor, because all operations should be finished by that point. We could cleanup the grid like ShardingMongodTestFixture or simply make sure the catalog cache executor is shutdown and joined on the ShardingTestFixture destructor. |
| Comments |
| Comment by Githook User [ 27/Aug/20 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |