[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: |
|
||||||||||||||||
| 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. |