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

If _recvChunkCommit throws an exception we don't properly roll back the migration

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.2.2, 2.3.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL

      If _recvChunkCommit throws an exception we abort the in-progress migration, but don't properly set the version on the donor shard back to what it was before the migration started. This leaves the cluster in an inconsistent state that can't process queries because all setShardVersion calls fail.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: