[SERVER-48098] Run scheduled jobs before destroying ServiceContext Created: 11/May/20 Updated: 29/Oct/23 Resolved: 24/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||
| Sprint: | Sharding 2020-06-29 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
ShardingTestFixture inherits from ServiceContextTest and ShardingTestFixtureCommon. Since ShardingTestFixtureCommon maintains a task executor that could run jobs scheduled from here, the destructor for ServiceContext must always be called after all jobs scheduled on the executor are retired. This ensures no client thread exists when unit-tests attempt to destroy the service context. |
| Comments |
| Comment by Githook User [ 24/Jun/20 ] |
|
Author: {'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com', 'username': 'saltzm'}Message: |