Handle choosing a new donor node when a startApplyingOpTime exists

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Repl 2021-01-11, Repl 2021-01-25, Repl 2021-02-08
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Xuerui Fa
              Reporter:
              Matthew Russotto
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: