[SERVER-39473] Should not report isMaster while stepping down conditionally Created: 08/Feb/19 Updated: 29/Oct/23 Resolved: 21/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| 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 | ||||||||||||
| Sprint: | Repl 2019-02-25 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 19 | ||||||||||||
| Description |
|
We currently report isMaster: false while in the process of stepping down unconditionally (but not while stepping down conditionally). We should report isMaster: false whenever we are stepping down. We cannot accept writes while the stepdown is in process. If the stepdown ultimately fails, we can just report isMaster: true again. |
| Comments |
| Comment by Githook User [ 21/Feb/19 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@10gen.com', 'username': 'mtrussotto'}Message: |