[SERVER-35245] Stepping Down Primary should not cause Initial Sync to fail Created: 25/May/18 Updated: 06/Dec/22 Resolved: 06/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.4.15, 3.6.5, 4.0.0-rc0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Arnie Listhaus | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | initialSync | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
Summary As part of the stepDown process, all current operations are killed and this would include an initial sync which is in progress.
Justification Although, it is possible to modify the sync source for an initial sync at startup as of 3.4, once an initial sync is running, we are unable to change the sync source. If a primary is under load with an initial sync running, it may be desirable for a customer to want to elect another primary leaving the initial sync running against the original primary node. |