[SERVER-48037] two_nodes_priority_takeover.js should run replSetReconfig command directly instead of using reconfig helper Created: 08/May/20 Updated: 29/Oct/23 Resolved: 08/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc5, 4.7.0 |
| 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.4
|
||||||||||||||||
| Sprint: | Repl 2020-05-18 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 13 | ||||||||||||||||
| Description |
|
The two_nodes_priority_takeover.js test does a reconfig to swap the priority of two nodes in a replica set, and then expects the new, higher priority node to take over and become primary. Right now, it uses this reconfig helper which may execute a single config change as a series of multiple reconfigs. This makes the test unstable, since the final reconfig executed by that helper may occur after the priorities have switched, so it may interfere with the nodes stepping down. We should execute the reconfig with a plain reconfig command so it can happen in a single step and avoid this issue. |
| Comments |
| Comment by Githook User [ 08/May/20 ] |
|
Author: {'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}Message: (cherry picked from commit 09b1be8b2f4c69c5d942ceb2736c449cefabcb65) |
| Comment by Githook User [ 08/May/20 ] |
|
Author: {'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}Message: |