Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11599

Docs for SERVER-33295: Kill long-running snapshot transactions

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.4
    • Affects Version/s: None
    • Component/s: Server
    • Labels:

      Documentation Request Summary:

      Added a new server parameter transactionLifetimeLimitSeconds. Settable on startup and via setParameter, retrievable via getParameter. Defaults to 60 seconds. Minimum acceptable value is 1 second. Only useful on storage engines that support transactions.

      Dictates the lifetime given to each transaction, after which a periodic (runs every transactionLifetimeLimitSeconds/2 seconds, or at most once per second and at least once per minute) background thread will find and abort the transaction.

      Each transaction maintains a snapshot of the storage engine data at a point in time, requiring the storage engine to maintain that history all the way back to that point in time, which has the potential to fill up its cache and immobilize the system. Users may also forget to commit transactions, in which case they should be cleaned up eventually. Transactions therefore must expire to preempt storage cache pressure immobilizing the system.

      Scope of changes:

      • Parameter page
      • added a Production Consideration section
        • runtime limit section
        • actively abort when abandoning transactions
      • Release notes

      Impact to other docs outside of this product:




      Engineering Ticket Description:

      From the design,

      The "oldest" open transaction in WiredTiger will pin write history in cache until it finishes. Here, "oldest" means the read timestamp is the earliest of any open transaction on the system. Any write history with a timestamp equal to or newer than this read timestamp must stay pinned in cache, in order to serve the open transaction. We need a way to prevent these transactions from staying open too long, in order to prevent cache pressure from becoming too extreme."

      Adding a transactionLifetimeLimitSeconds server parameter, which can be set at startup and via setParameter. Transaction will now expire, per the server parameter, and be asynchronously periodically cleaned up.

            kay.kim@mongodb.com Kay Kim (Inactive)
            kay.kim@mongodb.com Kay Kim (Inactive)
            0 Vote for this issue
            2 Start watching this issue

              5 years, 39 weeks, 3 days ago