[SERVER-40795] Always execute ThreadPoolTaskExecutor callbacks on thread pool threads Created: 23/Apr/19 Updated: 29/Oct/23 Resolved: 24/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Service Arch 2019-04-22, Service Arch 2019-05-06 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 5 | ||||||||||||||||
| Description |
|
Rather than relying on failure to schedule work onto the background thread pool as the mechanism for failing scheduled (but not run callbacks), wait to join the executor until after all jobs have cleared through. I.e. join the thread pool in task executor join(), after all pool processing jobs are gone, instead of in shutdown() |
| Comments |
| Comment by Githook User [ 24/Apr/19 ] |
|
Author: {'email': 'jcarey@argv.me', 'name': 'Jason Carey', 'username': 'hanumantmk'}Message: Rather than relying on failure to schedule work onto the background I.e. join the thread pool in task executor join(), after all pool |