[SERVER-22291] ReplicationCoordinatorImpl::_requestRemotePrimaryStepdown doesn't work Created: 25/Jan/16 Updated: 07/Feb/17 Resolved: 17/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.13, 3.3.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Judah Schvimer |
| Resolution: | Done | 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: |
v3.2
|
||||||||||||
| Sprint: | Repl 13 (04/22/16), Repl 14 (05/13/16), Repl 15 (06/03/16) | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This generates a stepdown command which fails:
This is called by a member with a higher priority that is not currently the primary so it can have a change to do a priority takeover, and to be elected. The fact that this is currently broken doesn't affect the system because the primary will also step-down on its own when it sees a higher priority member that can be elected. Fixing this might improve the timeliness of the step-down and forthcoming election. |
| Comments |
| Comment by Githook User [ 06/Feb/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: The command was passed the wrong arguments such that the stepdown (cherry picked from commit 668858332ad67678eaae2f9e3c5ff8ff66aa2b2c) |
| Comment by Githook User [ 17/May/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: The command was passed the wrong arguments such that the stepdown |