Avoid killing opCtx while holding the SessionCatalog mutex

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v5.0
    • Sharding 2021-07-12
    • 127
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Killing an opCtx triggers the execution of tasks scheduled on its baton (see here). Some of those tasks may acquire locks, and this acquisition could violate the hierarchical lock acquisition invariants in the context of SessionCatalog.

      Currently, the SessionCatalog kills operations (here) while holding a level 0 mutex (here). This ticket should change this behavior and have the operation killed without holding the SessionCatalog mutex.

              Assignee:
              Janna Golden
              Reporter:
              Amirsaman Memaripour
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: