[SERVER-52690] Switch ReshardingCollectionCloner to run on a separate TaskExecutor Created: 09/Nov/20  Updated: 29/Oct/23  Resolved: 10/Nov/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-data-clone
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-49291 Abort resharding operation if collect... Closed
Related
is related to SERVER-49787 Create collection bulk loader for res... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-11-16
Participants:

 Description   

The changes from ff6685c as part of SERVER-49787 had the ReshardingCollectionCloner run on the current thread for convenience with the testReshardCloneCollection command. Switching the ReshardingCollectionCloner to run on a separate TaskExecutor is a prerequisite to integrating the ReshardingCollectionCloner into the RecipientStateMachine. The RecipientStateMachine's thread needs to react to the mongo::Futures returned from multiple components (including ReshardingCollectionCloner) that are running concurrently.



 Comments   
Comment by Githook User [ 10/Nov/20 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-52690 Run ReshardingCollectionCloner on a TaskExecutor.

Restructures the ReshardingCollectionCloner class to run on a separate
thread and returned a mongo::Future readied when the cloning procedure
has completed successfully or failed with an error.

Also enables the ReshardingCollectionCloner to insert documents in
batches of size > 1 in a single storage transaction. The
reshardingCollectionClonerBatchSizeInBytes server parameter can be used
to control the size of the insert batch.
Branch: master
https://github.com/mongodb/mongo/commit/4e4ebb8fef276c28011aebecf8a0ed12e69a9f9b

Generated at Thu Feb 08 05:28:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.