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

Make all lock acquisitions for transactions have 0 second timeout

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.0-rc0
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-03-26, Storage NYC 2018-04-09, Storage NYC 2018-03-12, Storage NYC 2018-04-23, Storage NYC 2018-05-07, Storage NYC 2018-05-21
    • 58

    Description

      Txns should do no waiting for locks, they should fail the lock acquisition immediately if there's any conflict. They should also abort the transaction if that happens.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34829 Drop pending reaper must not delete the _dropPendingNamespaces entry until after the drop occurs

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-34372 Drop collection command with majority write concern should wait until two-phase drop finishes

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34726 Deadlock with locally stashed transaction resources during profiling

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34800 The transaction aborter thread should acquire locks with a 0-second lock acquisition timeout

          • Major - P3 - Major loss of function.
          • Closed
          is documented by

          Task - A task that needs to be done. DOCS-11716 Docs for SERVER-33244: Make all lock acquisitions for transactions have 0 second timeout

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-34951 LockerImpl should invariant against active UninterruptibleLockGuard usage when _maxLockTimeout is set

          • Major - P3 - Major loss of function.
          • Backlog

          Task - A task that needs to be done. SERVER-34924 Treat LockTimeout as transient transaction error

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-35023 Add server parameter maxTransactionLockRequestTimeoutMillis test

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              dianna.hohensee@mongodb.com Dianna Hohensee
              spencer@mongodb.com Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: