[SERVER-29615] Allow the AsyncResultsMerger to be linked into mongod Created: 13/Jun/17  Updated: 30/Oct/23  Resolved: 23/Jun/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.5.10

Type: Improvement Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: Jason Chan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-29617 Use the AsyncResultsMerger to copy do... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

The AsyncResultsMerger was originally developed by the sharding team, for the purpose of merging multiple, remote cursor streams asynchronously and in parallel. Right now, it is only linked into mongos, but it could useful as a general purpose component if it was made less sharding specific and was able to be accessed from a mongod. One of the intended non-sharding uses of the ARM is for parallelizing the initial sync collection cloning process. Since one of its first uses will be for initial sync collection cloning, it may be good to add and instantiate an ARM in the CollectionCloner that is unused to begin with, as a way to verify that is usable on a mongod.



 Comments   
Comment by Githook User [ 23/Jun/17 ]

Author:

{u'name': u'Jason Chan', u'email': u'jason.chan@mongodb.com'}

Message: SERVER-29615 Allow the ARM to be linked to mongod
Branch: master
https://github.com/mongodb/mongo/commit/3bb0f6030b5609002049ea2156e97fe4c6c05d5d

Generated at Thu Feb 08 04:21:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.