-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Service Arch
The goal of this ticket is to evaluate whether we could change the destruction order of the closure in the ExecutorFuture class: right now is destroyed after setting the future as ready. This has caused some issues, like this one, where the code was assuming that the objects captured by the lamda were destroyed before setting the future as ready.
- depends on
-
SERVER-53538 Clarify semantics of when destructor runs for ExecutorFuture chains
- Closed
- is related to
-
SERVER-66126 Clear Future/ExecutorFuture continuations as they run
- Open
- related to
-
SERVER-54119 Destroy SharedStateBase as we unfold continuations
- Closed
-
SERVER-66254 Complete TODO listed in SERVER-52942
- Closed