-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.1.7
-
Component/s: Sharding
-
Fully Compatible
-
ALL
Currently renameCollection is just a passthrough command and does not involve the config server or take any distributed lock. This can potentially mess up the config metadata if it runs concurrently with shardCollection.
- is depended on by
-
SERVER-55637 Create random_DDL_CRUD_setFCV_operations FSM workload
- Closed
- is related to
-
SERVER-39464 Concurrent rename and shard collection causes shard collection to fail
- Closed