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

Detect inconsistent lock ordering

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.1.7
    • Component/s: Concurrency
    • None
    • Storage Execution
    • QuInt B (11/02/15)

      In order to avoid potential deadlocks, we require consistent ordering of lock acquisition/release. Currently there are no checks for these, and it is easy to accidentally introduce incorrect orderings. Moreover, there is a possibility that some of these can be extremely rare, potentially leading to deadlock.

      By checking lock ordering in debug builds, we can reduce the likelihood of such problems.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            geert.bosch@mongodb.com Geert Bosch
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: