[SERVER-7494] If _recvChunkCommit throws an exception we don't properly roll back the migration Created: 27/Oct/12  Updated: 11/Jul/16  Resolved: 16/Nov/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.2.2, 2.3.1

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

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.



 Comments   
Comment by Spencer Brody (Inactive) [ 27/Oct/12 ]

https://github.com/mongodb/mongo/commit/9fe3b3eb52c266723b4af1083b3351237f611e32

Generated at Thu Feb 08 03:14:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.