Release locks before DB refresh in rename coordinator

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Sharding EMEA 2021-05-31
    • 151
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In case of rename between DBs, the database and collection locks are acquired on the source collection before performing a check on the database that is not allowed to happen if locks are held.

      The test statement supposedly ensuring that rename between DBs works on the DDL coordinator, needs to be updated because it is wrongly renaming test.unSharded to test.otherDBSamePrimary.unsharded.

              Assignee:
              Pierlauro Sciarelli
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: