[SERVER-10434] difficult to cleanup databases not currently populated by chunks Created: 05/Aug/13 Updated: 06/Dec/22 Resolved: 23/Aug/18 |
|
| 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: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
It's currently hard (without direct access to shard servers) to cleanup databases that previously but not longer contain data for that database. This manifests as problems in reporting (listDatabases reports databases still exist after drop) and data size (empty databases take up space on disk). |
| Comments |
| Comment by Kaloian Manassiev [ 23/Aug/18 ] |
|
We understand metadata operations failing in the middle may leave partial data around and this is not an issue only with databases. Closing this ticket and we will revisit this when we work on using transactions or resumable task queue for metadata operations. |