[SERVER-4725] auto-migrates don't reload current sharding status... Created: 19/Jan/12  Updated: 11/Jul/16  Resolved: 17/Apr/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.1.1

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Brandon Diamond
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

...and therefore may fail to detect when a shard goes into draining mode, which could cause there to be data on the shard after it was removed.



 Comments   
Comment by auto [ 17/Apr/12 ]

Author:

{u'login': u'', u'name': u'Brandon Diamond', u'email': u'brandon@10gen.com'}

Message: SERVER-4725: reload sharding status before migrate
Branch: master
https://github.com/mongodb/mongo/commit/57d9a672dc4dda75e4bf36752678609f8ebce7da

Comment by Brandon Diamond [ 04/Apr/12 ]

Code written. Trying to think of a good way to test.

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