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

MigrationManager::CollectionMigrationsState doesn't need to hold onto the DistLockHandle value anymore

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding 2016-09-19

    Description

      Since the MigrationManager is using clusterId as a lock session id, which is what DistLockHandle is, there is no longer a need for MigrationManager::CollectionMigrationsState to store this value – it will be a constant lockSessionID for every balancer instance: there's a _lockSessionID local variable in MigrationManager.

      Remove the MigrationManager::CollectionMigrationsState struct's distLockHandle variable, and clean up the MigrationManager code a bit because it no longer needs to handle it.

      Attachments

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: