-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.2.0
-
Component/s: Aggregation Framework, Sharding
-
Query Optimization
-
(copied to CRM)
SERVER-18925 added the distribution of merge stage of aggregation to any random shard rather than overloading primary shard for the database.
On a very large cluster this can max out the number of connections when every shard can be sending data to every shard and therefore it's desirable to add ability to stick to primary shard or be able to limit the shards that can be delegated with this ability.
- related to
-
SERVER-27304 Create setParameter to make all aggregations which require merging select the primary shard as the merger
- Closed
-
SERVER-27283 Sharded aggregations that need merging should only consider for merging the shards that have documents to contribute
- Backlog
-
SERVER-18925 Merging part of aggregation pipeline should be performed on a random shard to distribute the load
- Closed