[SERVER-52942] Evaluate whether we could change the destruction order of the closure in the ExecutorFuture class Created: 19/Nov/20 Updated: 06/Dec/22 Resolved: 02/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Backlog - Service Architecture |
| Resolution: | Done | Votes: | 0 |
| Labels: | sa-remove-fv-backlog-22 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Matt Diener (Inactive) [ 02/May/22 ] |
|
Destructor ordering can be changed and we are starting to work on it with SERVER-66126. |