-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding EMEA 2021-05-31
-
151
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.