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

Update Locker _threadId when stashing/unstashing

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.6
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-04-09, Storage NYC 2018-04-23
    • 13

      For debugging, the Locker class has a _threadId member that is displayed when the lock manager dumps a lock report. To avoid confusion when using the report for diagnosis, we should ensure that this member is updated when Lockers are taken out of their originating OperationContext and stashed, and then updated again when unstashed and assigned to a new thread with a new OperationContext.

            Assignee:
            james.wahlin@mongodb.com James Wahlin
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: