[SERVER-40794] TaskExecutor should support creating CallbackHandles before scheduling work Created: 23/Apr/19 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Service Arch 2019-04-22 | ||||||||
| Participants: | |||||||||
| Description |
|
Right now users of TaskExecutor that need to work with CallbackHandles have to work around an inherent race between dealing with the returned Handle and the callback which may be running. This race could be avoided if it was possible to create the CallbackHandle in advance then tell the TaskExecutor to use it. An additional goal to achieve in the process of this work is to, instead of taking a callback, return a future when a CallbackHandle is provided ahead of time. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ] |
|
We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. |
| Comment by A. Jesse Jiryu Davis [ 30/Apr/19 ] |
|
redbeard0531 should we close this wontfix, or rename it to "Make TaskExecutor inherit from OutOfLineExecutor"? |