[SERVER-27673] add support to CollectionCloner for smaller batch sizes Created: 13/Jan/17  Updated: 06/Dec/22  Resolved: 30/May/17

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

Type: Improvement Priority: Minor - P4
Reporter: Benety Goh Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-29196 collection cloner only sets batchSize... Closed
Related
related to SERVER-27611 DatabaseCloner::shutdown() does not s... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Participants:

 Description   

This makes it easier to reproduce issues seen in production relating to large collection clones interrupted midway.



 Comments   
Comment by Judah Schvimer [ 24/Mar/17 ]

We should also do this for the OplogFetcher.

Comment by Judah Schvimer [ 13/Jan/17 ]

After adding this option, we should reduce the batch size in the initial sync and resync passthroughs to hit any batching bugs.

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