[SERVER-4477] Interrupting compact can cause drop of collection indexes Created: 13/Dec/11 Updated: 15/Dec/17 Resolved: 18/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
[ed: original title "Should compact always leave indexes intact?"] Right now, compact immediately drops indexes, so if there's an error or someone kills the operation, you end up with a collection with no indexes, which can be very inconvenient (especially on a secondary). |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 18/Sep/12 ] |
|
Nearly impossible, as then you'd have to make all the index changes. |