[SERVER-37611] Reconsider implementation of TransactionCoordinator removal from catalog Created: 12/Oct/18  Updated: 27/Dec/18  Resolved: 27/Dec/18

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: Won't Fix Votes: 0
Labels: ShardedTxn:DistributedCommit, transaction-coordinator-management
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Right now TransactionCoordinators are reactively removed from the TransactionCoordinatorCatalog when they transition to either committed or aborted. However, this removal is not atomic with the action that commits or aborts the coordinator, which makes reasoning about coordinator lifetime somewhat different. Though the current implementation is okay, I'm creating this ticket to track whether there's a way to do this that's a little better or less error prone.


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