[SERVER-54146] Stop replication can happen in wrong order for catchup.js Created: 29/Jan/21 Updated: 09/Apr/21 Resolved: 09/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Samyukta Lanka |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2021-02-22, Repl 2021-03-08, Repl 2021-03-22, Repl 2021-04-05, Repl 2021-04-19 | ||||
| Participants: | |||||
| Linked BF Score: | 143 | ||||
| Description |
|
Catchup.js calls stopReplicationAndEnforceNewPrimaryToCatchUp. But we don't enforce the ordering that replication is stopped, so the node that we want to elect could be stopped first, meaning that its data is not fresh enough to be elected. |
| Comments |
| Comment by Samyukta Lanka [ 09/Apr/21 ] |
|
Closing in favor of |