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

[required cleanup] Tenant migration donor code creates a new TaskExecutor for each TenantMigrationAccessBlocker

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • Sharding

    Description

      Currently a new TaskExecutor is created and given to each TenantMigrationAccessBlocker, and the TenantMigrationAccessBlocker only uses it to wait for the commit or abort OpTime to become majority committed.

      At the very least, all TenantMigrationAccessBlockers should share a single executor, but we should also think about whether we can avoid creating a separate executor just for this.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: