[SERVER-41221] rollback_after_enabling_majority_reads.js test should make sure the final rollback occurs on node 0 Created: 17/May/19 Updated: 29/Oct/23 Resolved: 04/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 4.1.11 |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | William Schultz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||
| Sprint: | Repl 2019-06-17, Repl 2019-07-01, Repl 2019-07-15, Repl 2019-07-29, Repl 2019-08-12, Repl 2019-08-26, Repl 2019-09-09 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The rollback_after_enabling_majority_reads.js test runs a final rollback here after restarting node 0 with EMRC=true. It intends for the rollback to occur on node 0, but since node 0 is a SECONDARY at the time it is restarted with EMRC=true, the RollbackTest fixture will end up running the rollback on node 1. We should consider shutting down and restarting node 1 to let node 0 become primary again before initiating the final rollback sequence. |
| Comments |
| Comment by Githook User [ 25/Sep/19 ] |
|
Author: {'username': 'will62794', 'email': 'william.schultz@mongodb.com', 'name': 'William Schultz'}Message: (cherry picked from commit c926176630da106f30b84f69cba036c2e4963758) |
| Comment by Githook User [ 03/Sep/19 ] |
|
Author: {'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}Message: |