[SERVER-25047] Create initial sync test that uses failpoint to make initial sync fail and retry during apply ops Created: 13/Jul/16 Updated: 13/Sep/16 Resolved: 13/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Repl 18 (08/05/16), Repl 2016-08-29, Repl 2016-09-19 | ||||
| Participants: | |||||
| Description |
|
We don't currently have any jstests that test initial sync failing and retrying. We should add a failpoint that causes initial sync to fail during apply ops and then create a test that triggers it and tests that initial sync retries and succeeds. |
| Comments |
| Comment by Judah Schvimer [ 13/Sep/16 ] |
|
This is already tested in initial_sync_fail_insert_once.js and will be tested more thoroughly in unittests. |
| Comment by Scott Hernandez (Inactive) [ 13/Jul/16 ] |
|
I think you can do this without a fail-point and as a DataReplicator unit test |