[SERVER-18925] Merging part of aggregation pipeline should be performed on a random shard to distribute the load Created: 11/Jun/15 Updated: 06/Dec/16 Resolved: 07/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Sharding |
| Affects Version/s: | 3.0.5 |
| Fix Version/s: | 3.1.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | James Cohan |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Quint Iteration 7 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 07/Aug/15 ] |
|
Author: {u'username': u'jamesfcohan', u'name': u'James Cohan', u'email': u'james.cohan@10gen.com'}Message: |