SERVER-135753Backlog

Investigate whether the execution ticket can be released independent of a nested non-global lock wait

* 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 exe

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.