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

Possible for TransactionParticipant to never get cleaned up if no write happened

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 4.1.4
    • Fix Version/s: 4.1.12, 4.0.13
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0
    • Sprint:
      Sharding 2018-12-31, Sharding 2019-03-25, Sharding 2019-05-06, Sharding 2019-05-20
    • Case:

      Description

      If a TransactionParticipant was created but never successfully persisted any changes to config.transactions, it can stay alive indefinitely. The most likely case for this to occur is when session is exclusively used for read only transactions. This is because the transaction reaper only looks at the config.transactions collection when deciding which transactions to reap.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: