[SERVER-39349] Recovering the state of a completed single-shard transaction should not block Created: 01/Feb/19  Updated: 29/Oct/23  Resolved: 29/Apr/19

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

Type: Improvement Priority: Major - P3
Reporter: Shane Harvey Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-39726 Recovering the state of an uncommitte... Closed
Related
related to SERVER-39187 Rerunning commitTransaction on a new ... Closed
related to SERVER-37344 Implement recovery token for retrying... Closed
is related to SERVER-39726 Recovering the state of an uncommitte... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-04-08, Sharding 2019-04-22, Sharding 2019-05-06
Participants:

 Description   

Opening in response to the single-shard transaction behavior described in SERVER-39187 and SERVER-37344:

single shard transactions don't send coordinateCommit. And the current behavior is that attempting to recover a single shard transaction commit will make it wait for the coordinator to timeout and then check for the commit state of the transaction locally.

It would be a great improvement if recovering the state of a committed/aborted single-shard transaction did not block for 60 seconds (or transactionLifetimeLimitSeconds).

CC: alyson.cabral.



 Comments   
Comment by Githook User [ 29/Apr/19 ]

Author:

{'email': 'randolph@10gen.com', 'name': 'Randolph Tan', 'username': 'renctan'}

Message: SERVER-39349 Recovering the state of a completed single-shard transaction should not block
Branch: master
https://github.com/mongodb/mongo/commit/72ff70c9e4e3a1f3b5323ffc49d5da5289eb7644

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