[SERVER-12147] Removing duplicate index cause corrupt database Created: 17/Dec/13 Updated: 10/Dec/14 Resolved: 20/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.4.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Christianna Szwajkowski | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
virtual, linux x86 64 |
||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Comments |
| Comment by Ramon Fernandez Marina [ 20/Jun/14 ] |
|
cszwajkowski, apologies for the late reply. This behavior was reported in |
| Comment by Christianna Szwajkowski [ 17/Dec/13 ] |
|
We found some duplicate indexes for a collection in our database. We don't know how it happened, but it was creating some issues with queries. Dropping the indexes corrupted the database. I had taken a snapshot of the database before dropping the indexes. Restoring this snapshot on my machine cleaned the duplicate indexes and it is working fine. I am attaching a screenshot that shows the duplicate indexes and the exception that it threw after dropping them. Here is a link where somebody explains how they were able to re-produce this issue: |