[SERVER-31522] stepUp helper should call AwaitNodesAgreeOnAppliedOpTime after primary writes "new primary" op Created: 11/Oct/17 Updated: 27/Oct/23 Resolved: 17/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Calling awaitNodesAgreeOnPrimary first is probably good, but not sufficient since it doesn't actually wait for the primary to be able to accept writes. getPrimary() uses isMaster and should wait for the primary to be able to accept writes. |
| Comments |
| Comment by Judah Schvimer [ 17/Apr/20 ] |
|
The related BF was fixed in another way. We can reopen this ticket if it's needed to fix a different BF. |