[SERVER-38320] Handle a TransactionCoordinator's OperationContext being killed by a user Created: 29/Nov/18  Updated: 29/Oct/23  Resolved: 17/Jan/19

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

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-12-17, Sharding 2018-12-31, Sharding 2019-01-14, Sharding 2019-01-28
Participants:

 Comments   
Comment by Githook User [ 17/Jan/19 ]

Author:

{'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi'}

Message: SERVER-38320 Handle a TransactionCoordinator's OperationContext being killed by a user
Branch: master
https://github.com/mongodb/mongo/commit/b956c24930044004fb229adc52e34f20d81a36bb

Comment by Matthew Saltz (Inactive) [ 27/Dec/18 ]

I think it may make sense to wait for SERVER-38522 before doing this, since that will potentially change how we interact with OperationContexts from the coordinator

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