[SERVER-52720] Handle choosing a new donor node when a startApplyingOpTime exists Created: 09/Nov/20 Updated: 29/Oct/23 Resolved: 05/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Xuerui Fa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-D | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2021-01-11, Repl 2021-01-25, Repl 2021-02-08 | ||||||||
| Participants: | |||||||||
| Description |
|
In TenantMigrationRecipientService, when a startApplyingOpTime exists in the state, the new donor node must have a majority snapshot optime greater than or equal to the startApplyingOpTime. If it does not the new donor node must be excluded for a configurable amount of time (default: 1 minute) and another node selected. We should not fail the migration just because no suitable nodes are available "right now"; instead, we should keep waiting until a suitable node becomes available. |
| Comments |
| Comment by Githook User [ 05/Feb/21 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: |