[SERVER-31277] Cancel all user operations on heartbeat stepdown path Created: 26/Sep/17 Updated: 30/Oct/23 Resolved: 16/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||
| Sprint: | Repl 2017-10-02, Repl 2017-10-23 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently we cancel all running operations associated with an incoming connection when we receive the replSetStepDown command, but we don't do the same for when we step down due to our liveness information. We should also cancel ongoing operations for those stepdowns, to A) bring the behavior of the two stepdown paths into alignment and B) protect against an operation that starts when we are primary, yields, we step down, then step back, then the operation resumes. |
| Comments |
| Comment by Githook User [ 16/Oct/17 ] |
|
Author: {'email': 'spencer@mongodb.com', 'name': 'Spencer T Brody', 'username': 'stbrody'}Message: |