[SERVER-27163] resync command should set STARTUP2 after stopping data replication Created: 22/Nov/16 Updated: 06/Dec/22 Resolved: 09/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Replication Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Operating System: | ALL |
| Sprint: | Sharding 2017-01-02, Sharding 2017-02-13, Sharding 2017-03-06 |
| Participants: |
| Description |
|
Currently it sets follower mode to STARTUP2 before stopping data replication. This can lead to a race with the data replication threads which also set the follower mode. If they set the follower modes after the resync command, we would be doing an initial sync in a different follower mode. |
| Comments |
| Comment by Siyuan Zhou [ 09/Apr/20 ] |
|
Resync command is deprecated in |
| Comment by Mathias Stearn [ 30/Nov/16 ] |
|
This also changes the member state to something that isn't readable() while we are potentially in steady-state replication. |