Recovering the state of a completed single-shard transaction should not block

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.11
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2019-04-08, Sharding 2019-04-22, Sharding 2019-05-06
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Randolph Tan
            Reporter:
            Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: