Remove all instances of UninterruptibleLockGuard

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • Execution Team 2022-11-14, Execution Team 2022-12-12, Execution Team 2022-11-28
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Uses of UninterruptibleLockGuard indicate places in the code that do not comply with MongoDB's requirement that all operations be interruptible at places where they block to wait for resources. Every one of them is a potential future deadlock, and adds complexity to other parts of the codebase. We should reimplement codepaths that depend on UninterruptibleLockGuard so as to be interruptible.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Andy Schwerin
              Votes:
              1 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: