[SERVER-21720] rollback4.js doesn't test rollback unless secondary falls behind Created: 01/Dec/15 Updated: 06/Dec/22 Resolved: 20/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Replication Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Operating System: | ALL |
| Participants: |
| Description |
|
It does a 1 million inserts then shuts down the primary. If the secondary was able to keep up, when the primary is restarted there will be no rollback. It should halt replication on the secondary either by shutting it down or using the failpoint. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 20/Jul/17 ] |
|
This test was removed in |