[SERVER-40500] Make initial_sync_test_fixture_test.js robust to network errors Created: 05/Apr/19 Updated: 06/Dec/22 Resolved: 26/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2019-10-21 | ||||
| Participants: | |||||
| Linked BF Score: | 17 | ||||
| Description |
|
Right now initial_sync_test_fixture_test.js expects each remote command during initial sync to only be issued once, but if one of the commands is retried because of a network error, the test will fail because it expects to see a different remote command. The test should be able to handle such a network error. |
| Comments |
| Comment by Samyukta Lanka [ 26/Sep/19 ] |
|
Resumable Initial Sync won't fix this because it has to do with the test being able to deal with retries of commands due to network errors. Since we don't make other tests be able to handle network errors, closing this as won't fix. |
| Comment by Judah Schvimer [ 26/Sep/19 ] |
|
Will this be fixed with Resumable Initial Sync? |