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

Audit uses of database exclusive locks in DDL operations

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None

      Most DDLs (create, rename, drop, collMod, etc.) shouldn't need to take an exclusive (MODE_X) database or global lock, but can instead take an intent exclusive (MODE_IX) database lock and take finer-grained locks over the affected collections. 

      Taking an exclusive database lock blocks all other operations, and can lead to performance problems (e.g. SERVER-72703) or deadlocks (e.g. SERVER-103744).

       

      This ticket is for auditing the current uses of MODE_X database (or global) locks in DDLs and opening tickets if they can be replaced with more fine-grained locks.

            Assignee:
            Unassigned Unassigned
            Reporter:
            joan.bruguera-mico@mongodb.com Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: