[SERVER-38346] [blocked on platforms] Update transaction coordinator to use SharedSemiFuture Created: 30/Nov/18  Updated: 27/Oct/23  Resolved: 22/Feb/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Works as Designed Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-36359 Improve usability of Futures with Exe... Closed
Participants:

 Description   

When we are able to chain continuations to SharedSemiFutures, we'll be able to simplify the implementation of the transaction coordinator's notification mechanism for callers waiting for the completion of commit.



 Comments   
Comment by Kaloian Manassiev [ 22/Feb/19 ]

There are probably many places which can benefit from the availability of SharedSemiFuture and we don't need to have tickets for each one of them. Closing this one in the interest of reducing backlog clutter.

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