[SERVER-6115] final migration can interfere with removal of database on draining shard Created: 18/Jun/12  Updated: 19/Mar/13  Resolved: 08/Mar/13

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

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

Attachments: File remove_with_migrate.js    
Issue Links:
Duplicate
duplicates SERVER-8838 removeRange() implicitly re-creates a... Closed
Operating System: ALL
Participants:

 Description   

See test case for repro - basic problem is that the cleanup from the final migration off a draining shard will re-create the database being drained even after the database is dropped externally. This prevents the shard from being re-added.



 Comments   
Comment by Greg Studer [ 20/Jun/12 ]

Fixed test, seems like something we may want to look at again in 2.3.

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