[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:
Depends
Related
related to SERVER-14985 Merge stages in aggregation should be... Closed
related to SERVER-27304 Create setParameter to make all aggre... Closed
related to SERVER-17737 Support distributed merger for aggreg... Open
is related to SERVER-24815 Merging aggregation pipeline strategy... Backlog
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: SERVER-18925 Enable pipeline merging to happen on random shard when possible
Branch: master
https://github.com/mongodb/mongo/commit/c54e23ccee372703cb2dc714762f9beaf4ad0e10

Generated at Thu Feb 08 03:49:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.