TenantMigrationRecipientService::Instance::interrupt() should be able to interrupt steps waiting for an opTime to be majority replicated.

XMLWordPrintableJSON

    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      (This is just an optimization ticket)

      Currently there are many places in instance task where it wait for an opTime to be majority replicated(like here). These waits are interrupted only during node step down but if TenantMigrationRecipientService::Instance::interrupt() gets called due to some oplog fetcher error, recipient shutdown or on receive recipientForgetMigration cmd, the opTime wait steps aren't interrupted.

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Suganthi Mani
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: