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

Investigate if we can ban upgrading the global lock

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Execution Team 2023-02-20, Execution Team 2023-02-06
    • 169

      Upgrading the global lock mode without first releasing the lock held can have bad side effects (namely deadlock and resource exhaustion). We've removed some cases where this can happen (most recently in SERVER-59219). We think we can explicitly ban this behavior in code, as it could help us identify additional bugs we haven't hit yet, and avoid future ones. That said, there are some instances where we currently upgrade the global lock, and we'll need to fix these first.

            Assignee:
            fausto.leyva@mongodb.com Fausto Leyva (Inactive)
            Reporter:
            dan.larkin-york@mongodb.com Dan Larkin-York
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: