[SERVER-1905] Database files not discarded from replica sets shards on a dropDatabase Created: 06/Oct/10 Updated: 07/Oct/10 Resolved: 07/Oct/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.6.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathieu Poumeyrol | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
On a sharded and replica-set setup, dropDatabase on a unsharded DB performs semantically correctly from the mongos interface but let the actual files behind on the replica disks. |
| Comments |
| Comment by Mathieu Poumeyrol [ 06/Oct/10 ] |
|
my mistake. it did. after... some time. sorry, please close this case. |