[SERVER-13285] aborted background index build results in system.index entry but no index Created: 19/Mar/14 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, MMAPv1 |
| Affects Version/s: | 2.6.0-rc1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Dannenberg | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Steps To Reproduce: | run out of space during a background index build |
| Participants: |
| Description |
|
If you run out of disk space the index build will be cancelled, but the entry is not removed from the 'system.index' collection. |
| Comments |
| Comment by Eric Milkie [ 11/Nov/16 ] |
|
I suspect this happens only with MMAPv1, but we should confirm that. |