[SERVER-37232] Reactively remove TransactionCoordinator from TransactionCoordinatorCatalog when it reaches state committed or aborted Created: 20/Sep/18  Updated: 29/Oct/23  Resolved: 04/Oct/18

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

Type: Task Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: ShardedTxn:DistributedCommit
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-10-08
Participants:

 Description   

SERVER-37177 allows getting a Future from a coordinator that will be signaled when it reaches state committed or aborted. We can use this in the catalog on coordinator creation in order to ensure that a coordinator is removed from the catalog when it reaches either of these states.



 Comments   
Comment by Githook User [ 04/Oct/18 ]

Author:

{'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com', 'username': 'saltzm'}

Message: SERVER-37232 Remove coordinator from catalog asynchronously on commit or abort
Branch: master
https://github.com/mongodb/mongo/commit/c405add0814ea4cc819588d26fe315369319e010

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