-
Type:
Improvement
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Sharding EMEA
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
SERVER-71365 introduced a new check to verify if the process participating to a sharded renameCollection is also acting as the coordinator of the DDL, which is based on a remote query to the sharding catalog.
Such remote query could be replaced with a local read of config.system.sharding_ddl_coordinators, looking for the document represents the state or the RenameCollectionCoordinator
- is caused by
-
SERVER-71365 nss.rename(newNss, dropTarget) should only emit a single oplog event through the primary shard for the renamed and dropped namespaces
-
- Closed
-
- related to
-
SERVER-77492 Complete TODO listed in SERVER-74719
-
- Blocked
-