[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: |
|
||||||||||||||||||||||||
| 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 |