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

Mixed version shard JS testing of MigrationManager

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding 17 (07/15/16), Sharding 18 (08/05/16)

      When the Balancer starts using the MigrationManager, we can add a failpoint at the end of _executeMigration and test that the expected migrations run each migration round. For example, if the several source shards are v3.2, then migrations for the same collection must run sequentially because each shard will take the distlock rather than the balancer.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: