-
Type:
Improvement
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Labels:None
-
Sharding
-
Sharding 18 (08/05/16), Sharding 2016-08-29
Currently, the CollectionShardingState is kept on a map, which tracks the set of {{Collection}}s on the server. We should instead make it a decoration on the Collection in order to avoid the separate map lookup and mutex.
This also better ties the lifetime of a collection with that of its sharding state and allows us to potentially prevent direct drop of sharded collections.
- depends on
-
SERVER-24664 Get rid of calls to ShardingState::getCollectionMetadata
-
- Closed
-
- is duplicated by
-
SERVER-31902 Reduce contention on ShardingState::_mutex for insert workloads
-
- Closed
-