Acquire the DDL lock over the target database on renameCollection

XMLWordPrintableJSON

    • Type: Bug
    • 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
    • 10
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, we are not acquiring the target database DDL lock on a renameCollection operation when the source DB differs from the target DB.

      We should take it to serialize the renameCollection operation with any other DDL operation acting over the targeted database.

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

              Created:
              Updated:
              Resolved: