[SERVER-33383] Execution of replSetStepDown can race with unconditional stepdown via heartbeat response Created: 17/Feb/18 Updated: 29/Oct/23 Resolved: 01/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.9, 3.7.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vesselina Ratcheva (Inactive) | Assignee: | Vesselina Ratcheva (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: |
v3.6
|
||||||||
| Sprint: | Repl 2018-02-26, Repl 2018-03-12 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
Successful executions of unconditional stepdowns supercede stepdown attempts in response to replSetStepDown, but the execution of the command will not be killed if it wasn't issued by a client. Nodes attempting a priority takeover in pv0 send this command to the primary. A possible solution might be to make TopologyCoordinator::prepareForStepDownAttempt return an error if a stepdown has already completed (in addition to the existing stepdown-in-progress check.) |
| Comments |
| Comment by Githook User [ 24/Sep/18 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: (cherry picked from commit 6168a6e7f5586ffc273888bec73b76c1184105bd) |
| Comment by Spencer Brody (Inactive) [ 18/Sep/18 ] |
|
Requesting backport to 3.6 as it makes the backport of |
| Comment by Githook User [ 01/Mar/18 ] |
|
Author: {'email': 'vesselina.ratcheva@10gen.com', 'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb'}Message: |