Allow sharding DDL operations to acquire DDL locks over multiple namespaces

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding EMEA
    • Fully Compatible
    • Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15, Sharding EMEA 2023-05-29
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We need to add the ability to acquire the DDL locks ordered by name for Databases and Collections resources independently.

      This is needed to prevent deadlocks on those DDL Coordinators that acquire more than one lock per database and/or collection (like renameCollection) once the ability to run concurrent DDL operations over the same database is enabled.

            Assignee:
            Silvia Surroca
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: