[SERVER-8838] removeRange() implicitly re-creates a database if database does not exist Created: 04/Mar/13  Updated: 04/May/17  Resolved: 04/May/17

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: Nathan Myers
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-8598 Add command to cleanup orphaned data ... Closed
is depended on by SERVER-8836 sharding/remove2.js failing on Window... Closed
Duplicate
duplicates SERVER-4724 removeShard needs to take into accoun... Closed
is duplicated by SERVER-6115 final migration can interfere with re... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-03-27, Sharding 2017-04-17, Sharding 2017-05-08
Participants:

 Description   

... need a non-racy open-if-database-exists context. This causes issues when we drop a database while migrations are still waiting for cleanup.



 Comments   
Comment by Nathan Myers [ 20/Apr/17 ]

There is no removeRange() function anymore. Its replacement does not exhibit this behavior.

Comment by Greg Studer [ 16/May/13 ]

Should be fixed by changes in SERVER-8598

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