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.
If _recvChunkCommit throws an exception we don't properly roll back the migration
- Votes:
-
0 Vote for this issue
- Watchers:
-
1 Start watching this issue
- Created:
- Updated:
- Resolved: