[SERVER-44597] Make last oplog fetcher for stop timestamp respect initial sync retry strategy Created: 13/Nov/19 Updated: 29/Oct/23 Resolved: 10/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2019-11-18, Repl 2019-12-02, Repl 2019-12-16, Repl 2019-12-30, Repl 2020-01-13 |
| Participants: |
| Description |
|
The lastOplogEntryFetcher for Stop Timestamp in initial sync currently retries a fixed number of times based on the numInitialSyncOplogFindAttempts. It must instead retry for a fixed amount of time based on initialSyncRetryPeriodSeconds. |
| Comments |
| Comment by Githook User [ 09/Jan/20 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |