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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Concurrency
    • None
    • Storage Execution
    • ALL
    • Execution EMEA Team 2023-07-24
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Yujin Kang Park
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: