[SERVER-25880] Initial sync should wait longer for a sync source during its first attempt Created: 30/Aug/16 Updated: 31/Aug/16 Resolved: 31/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Repl 2016-09-19 |
| Participants: |
| Description |
|
Initial sync only waits 10 seconds for a sync source, even when the node has never had a sync source. Nodes have to wait the election timeout before running for election, so very frequently (in most of our tests, for example), 10 seconds is not enough time for other nodes to find a sync source. |
| Comments |
| Comment by Judah Schvimer [ 31/Aug/16 ] |
|
When chaining is disallowed and this occurs, initial sync will recover on its own by retrying initial sync from the start. In testing we do not allow initial sync to restart, so the solution is to just increase the number of sync source selection retries using the parameters created in |
| Comment by Scott Hernandez (Inactive) [ 31/Aug/16 ] |
|
This is only an issue with replica sets where chaining is disallowed because a primary must be elected. |