[SERVER-30319] When requesting only 1 thread for initial sync, use the 'find' command instead of 'parallelCollectionScan' Created: 25/Jul/17 Updated: 30/Oct/23 Resolved: 17/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2017-08-21 |
| Participants: |
| Description |
|
Because the parallelCollectionScan is relatively untested and unproven, we want to ensure that in 3.6 users have a way to continue to use the 'find' command until such a time that the parallelCollectionScan has been more proven. To that end, if the system is configured to only request 1 cursor for initial sync anyway, we should use the 'find' command to generate that cursor rather then using parallelCollectionScan with maxCursors=1 |