If a rename finds that the target namespace exists, we expect mongod and mongos to return NamespaceExists error, but with mongos, depending on if the target is a sharded collection, it sometimes returns NamespaceExists error as expected, but sometimes returns an error without a dedicated error code.
- is related to
-
SERVER-60632 Inconsistent error on mongos when renameCollection target already exists
- Closed