Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-59525

TenantMigrationRecipientAccessBlocker isn't being initialized correctly on recovery

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.0.4, 5.1.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Repl 2021-09-20
    • 62

    Description

      When we reconstruct all access blockers, such as in the case of rollback, we are not initializing the TenantMigrationRecipientAccessBlocker to its correct state depending on whether _rejectBeforeTimestamp exists in the migration document.

      For example, when the migration is in the kDone state (migration has completed and been forgotten), we are not setting the TenantMigrationRecipientAccessBlocker to the kRejectBefore state even though the _rejectBeforeTimestamp exists.

      Attachments

        Activity

          People

            vishnu.kaushik@mongodb.com Vishnu Kaushik
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: