Migration cloner abort does not validate the session id

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.3.14
    • Affects Version/s: 3.3.12
    • Component/s: Sharding
    • Fully Compatible
    • ALL
    • v3.2
    • Sharding 2016-09-19
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The migration cloner abort sequence does not transmit or validate the migration session id. Because of this it is possible that one shard aborts migration, which has been started by a completely different donor shard.

      This bug is exacerbated in 3.3 because failure to execute the _recvChunkStart command is always followed-up by an abort. That way if two migrations with different donors, but the same recipient have the potential of conflicting with each other in which case one of the migrations will remain stuck.

              Assignee:
              Kaloian Manassiev
              Reporter:
              Kaloian Manassiev
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: