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

Potential race in migration can have an aborted migration consume MigrateStatus::_cloneLocs

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.8.0-rc2
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • Sharding 10 (02/19/16)

      There are cases where the donor shard can abort the migration without contacting the recipient shard. If it starts another migration before the recipient shard realizes it, then it can call _cloneMigrate against the donor shard and interfere with the new migration. A similar issue exist for _transferMods as well.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: