Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-66659

Abort internal transactions for the previous txnNumber when starting a new txnNumber

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc10, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding NYC 2022-05-30, Sharding NYC 2022-06-13

      Currently, the TransactionParticipant does not abort internal transactions for the previous txnNumber (i.e. retryable internal transactions) when starting a new txnNumber like it does for regular transactions. Those dangling in-progress transactions should not lead to any hang but they hold on to some resources so we may want to abort them.

            Assignee:
            jack.mulrow@mongodb.com Jack Mulrow
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: