[SERVER-44259] rollback_after_enabling_majority_reads.js test should wait for restarted node to be in SECONDARY state before running stepUp command Created: 25/Oct/19 Updated: 29/Oct/23 Resolved: 28/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, 4.2.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| 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-11-04 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
The rollback_after_enabling_majority_reads.js tries to stepUp a node after restarting it. But even after awaitNodesAgreeOnPrimary, the restarted node could still be in STARTUP2 state. Thus, the subsequent replSetStepUp could fail because "because member is not currently a secondary". |
| Comments |
| Comment by Githook User [ 28/Oct/19 ] |
|
Author: {'username': 'ldennis', 'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng'}Message: (cherry picked from commit dc35d37187c3629a0ff77548b21328624c09a9d9) |
| Comment by Githook User [ 28/Oct/19 ] |
|
Author: {'username': 'ldennis', 'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng'}Message: |