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

MigrationDestinationManager should explicitly wait for existing session migration thread to complete before restarting a new migration

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc5
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • v8.0
    • Cluster Scalability 2024-5-13
    • 127

      Currently, the wait happens implicitly when MigrationDestinationManager::start() replaces the old _sessionMigration with the newly created _sessionMigration. From BF-32882, it is possible for the _sessionMigration thread to remain uninterrupted and this wait can lead to a deadlock between stepdown, MigrationDestinationManager and SessionCatalogMigrationDestination. 

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: