[SERVER-15410] Batch fetch missing documents during initial sync, with retries Created: 26/Sep/14 Updated: 06/Dec/22 Resolved: 13/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Done | Votes: | 1 |
| Labels: | PM248 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
During the first oplog apply phase in initial sync any missing local documents need to be queried for upstream. This is currently done one at a time with a max retry rate of 1; Any error will fail the initial sync process. By changing the process to queue up these missing document queries and retry many times we can get past connectivity issues or temporary network failures, as well as improving performance by not slowing down the apply phase to fetch these documents. |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 13/Sep/19 ] |
|
Yes, |
| Comment by Judah Schvimer [ 12/Sep/19 ] |
|
jesse, can we close this gone away? |