-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding NYC
-
1
Clearing the filtering metadata will prevent concurrent* operations on the same node from completing without refreshing the routing metadata and seeing the latest incarnation of the collection. Clearing the filtering metadata must be "atomic" with the drop.
*Concurrent operations will wait behind the critical section, but can possibly slip in right after the collection has been dropped.
- related to
-
SERVER-55781 Verify shard version matches before allowing createIndexes in sharding opObserver
- Closed