[SERVER-66127] Introduce the LegacyDestructorOrderingTag on all existing continuation functions and log bugs to remove the tags 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:
Depends
is depended on by SERVER-66128 Implement guaranteed continuation des... Backlog
is depended on by SERVER-66129 Provide directions to clean up Legacy... Backlog
is depended on by SERVER-66126 Clear Future/ExecutorFuture continuat... Open
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 the first step of SERVER-66126.

In order to move towards "guaranteed destructor ordering", we need to tag all existing continuations to be using the legacy destructor ordering semantics.

Introduce a tag into the codebase that gets passed into all continuation functions.


Generated at Thu Feb 08 06:04:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.