ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      • Problem: when an operation already holds a ticket (from an earlier, broader lock acquisition, e.g. the global lock) and then blocks waiting on a second, narrower lock (e.g. a $merge target collection lock, or $collStats with waitForLock: true), it keeps holding the ticket for the entire time it's blocked. Confirmed via repro (a 4.2-second lock wait produced 4,224ms of ticket delinquency with no interrupt-side signal at all).
      • This is a ticket delinquency-only issue; the interrupt side exempts the wait.
      • Check whether the ticket can be safely released before entering that second lock wait, or if we can avoid holding a ticket while waiting for a lock. 

      It may be necessary to discuss this with Ian.

            Assignee:
            Kyle Burgess
            Reporter:
            Kyle Burgess
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: