[SERVER-66128] Implement guaranteed continuation destructor ordering Created: 02/May/22 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Diener (Inactive) | 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
|
||||||||||||||||
| Sprint: | Service Arch 2022-05-16, Service Arch 2022-05-30, Service Arch 2022-06-13, Service Arch 2022-06-27, Service Arch 2022-07-11, Service Arch 2022-07-25, Service Arch 2022-08-08 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
This is a part of SERVER-66126. Continuations that get created without LegacyDestructorOrderingTag should clean up before running the next continuation in the chain. This should apply to both Future and ExecutorFuture. |
| Comments |
| Comment by Matt Diener (Inactive) [ 11/Aug/22 ] |
|
Putting this work on hold because it depends on a few conversations around workload management and the way we're going to move forward with Executors, Futures, Error Handling, etc. We're not currently in a place where our confidence around this topic is good enough for us to ask a bunch of folks to audit all of their continuation chains. Instead I'm spending some time to do a write-up on the topic and propose some options. |
| Comment by Githook User [ 26/May/22 ] |
|
Author: {'name': 'Matt Diener', 'email': 'matt.diener@mongodb.com', 'username': 'mattdiener'}Message: SERVER-66128 Add Policy to Future Func-using API |