[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:
Depends
depends on SERVER-53538 Clarify semantics of when destructor ... Closed
Related
related to SERVER-54119 Destroy SharedStateBase as we unfold ... Closed
related to SERVER-66254 Complete TODO listed in SERVER-52942 Closed
is related to SERVER-66126 Clear Future/ExecutorFuture continuat... Open
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.

Generated at Thu Feb 08 05:29:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.