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

LockerImpl should invariant against active UninterruptibleLockGuard usage when _maxLockTimeout is set

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Catalog and Routing
    • Storage NYC 2019-02-11, Execution Team 2020-01-13

      This is follow up work for SERVER-33244, to add a max lock acquisition timeout override (_maxLockTimeout) for transactions in order to prevent transactions from deadlocking with one another.

      UninterruptibleLockGuard cannot be used in transaction operation code paths if we wish to prevent deadlocks. However, query currently uses UninterruptibleLockGuard in the find/agg code paths. So this work is blocked on the completion of SERVER-33575, to remove UninterruptibleLockGuard usages from query code paths.

            yuhong.zhang@mongodb.com Yuhong Zhang
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            0 Vote for this issue
            9 Start watching this issue