-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.0.5
-
Component/s: Aggregation Framework, Sharding
-
None
-
Fully Compatible
-
Quint Iteration 7
Currently the merging step of the pipeline is always performed on the primary shard for that database, but there is no reason it has to be. To help distribute the load, it should be sent to a random shard.
- is related to
-
SERVER-24815 Merging aggregation pipeline strategy should be configurable
- Backlog
- related to
-
SERVER-14985 Merge stages in aggregation should be distributed beyond primary shard
- Closed
-
SERVER-27304 Create setParameter to make all aggregations which require merging select the primary shard as the merger
- Closed
-
SERVER-17737 Support distributed merger for aggregation queries
- Open