[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:
Duplicate
duplicates SERVER-9856 No check for building identical backg... Closed
duplicates SERVER-10895 Duplicate indexes being created at th... Closed
Operating System: ALL
Participants:

 Comments   
Comment by Ramon Fernandez Marina [ 20/Jun/14 ]

cszwajkowski, apologies for the late reply. This behavior was reported in SERVER-10895, which is actually a duplicate of SERVER-9856 and was fixed in version 2.4.5. If you haven't upgraded yet, I'd recommend you upgrade to 2.4.10.

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:
http://comments.gmane.org/gmane.comp.db.mongodb.user/93085

Generated at Thu Feb 08 03:27:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.