Make TenantMigrationAccessBlocker::abort not invariant that the migration is in blocking state

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Sharding 2020-09-07
    • 21
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, TenantMigrationAccessBlocker::abort has an invariant that the migration must have started blocking reads and writes when the migration aborts. That invariant should be removed because the migration could abort in any state. It could abort if it couldn’t find the recipient host when sending the first recipientSyncData so that case _access would kAllow. 

              Assignee:
              Cheahuychou Mao
              Reporter:
              Cheahuychou Mao
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: