[SERVER-23603] Dropping Index in WT Corrupted Database Created: 07/Apr/16 Updated: 06/Dec/22 Resolved: 08/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | John Page | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Running WiredTiger with a large "2d" index on a co-ordinate pair on field p as foreground. Dropped the original index - database quit immediately.
Database is WT runnign with nojournal - however as I understand it this can at worst lead to 60s of data loss/rollback. Database available for inspection in-situ on AWS. |
| Comments |
| Comment by Alexander Gorrod [ 08/Feb/17 ] |
|
john.l.page@mongodb.com Without more specific steps it would be very difficult to reproduce this failure. I'm going to close the ticket for now. If you encounter the problem again please reopen. |
| Comment by John Page [ 19/Jan/17 ] |
|
This was nearly a year ago so I have no idea exactly what version it was, should be easy to reproduce to test though. |
| Comment by Michael Cahill (Inactive) [ 11/Apr/16 ] |
|
john.page, what version of MongoDB are you running? There were several durability bugs fixed in |
| Comment by John Page [ 07/Apr/16 ] |
|
My Guess is that the _mdb_catalog.wt has reverted to when the index existed - but it no longer does. |