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

TransactionReaper and periodic transaction abort thread shouldn't abort transactions on secondaries

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.9
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25, Sharding 2019-03-11

      Description

      Periodic transaction killer kills unprepared transactions that run longer than 60 seconds. It shouldn't kill transactions on secondaries. Currently, it's very unlikely to have transactions in "kInProgress" state longer than 60 seconds on secondaries since such transactions become prepared right after applying all their write operations; this will be more likely when we start to support transactions consisting of multiple oplog entries.

      Session reaper and other periodic threads may have the same issue and need auditing.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matthew.saltz Matthew Saltz
              Reporter:
              siyuan.zhou Siyuan Zhou
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: