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

Lock acquisitions won't aways obey the OpContext's deadline or interruption

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Concurrency
    • None
    • Storage Execution
    • ALL

    Description

      There are multiple lock manager RAII classes which take both OperationContext and Locker (or both) in addition to a deadline argument. The behaviour of whether the OpContext's deadline will be obeyed seems dependent on what combination is passed for these three. For example, passing OpCtx=nullptr, Locker, deadline=Date_t::max() will not obey the deadline of the operation, because the OpContext is not passed down to the waiting method of the lock manager.

      We have runWithDeadline methods on the OperationContext which will allow us to not have to pass the deadline explicitly.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              kaloian.manassiev@mongodb.com Kaloian Manassiev
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: