[SERVER-27443] Fatal assertion 18506 DuplicateKey E11000 duplicate key error dup key Created: 16/Dec/16 Updated: 09/Oct/17 Resolved: 15/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | davy | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: |
|
| Participants: |
| Description |
|
I hava a replSet with 3 servers, there are with 300GB data, Last week, we suddenly had a power outage, when the power was restored, I restart my mongoDB successed, but when I cmd "show dbs;", I remeber it said like this: How can I fix it? Please help me. |
| Comments |
| Comment by Kelsey Schubert [ 15/Sep/17 ] |
|
Hi davy, I've completed our investigation. Unfortunately, from the data provided, we have not be able to conclusively determine the root cause of this issue. That said, from the evidence I've examined, I suspect that this issue originated in the storage layer beneath MongoDB/WiredTiger. Kind regards, |
| Comment by Kelsey Schubert [ 24/May/17 ] |
|
Hi davy, Sorry for letting this reply slip through the cracks. Unfortunately, a preliminary analysis did not reveal the root cause of this issue. We intend to do a thorough manual inspection of the bits in these files, however, this takes a significant amount of time and has to be scheduled against other work. If you encounter this issue again, please let us know so we can reprioritize this investigation. Kind regards, |
| Comment by davy [ 22/Dec/16 ] |
|
Hi Thomas, Is there too much difficulty? please tell me。 |
| Comment by Kelsey Schubert [ 19/Dec/16 ] |
|
Thanks for the upload. We have the files included in mongolog.tar, and are investigating. |
| Comment by davy [ 19/Dec/16 ] |
|
Sorry Thomas, I didnot reply to you Immediately. I click your portal, but I am not sure it successed... for you question: dbdir nearly 300GB, upload it Not realistic |
| Comment by Kelsey Schubert [ 16/Dec/16 ] |
|
Would you please also clarify which versions, if any, of MongoDB you were running prior to MongoDB 3.0.0 in this replica set? Thanks, |
| Comment by Kelsey Schubert [ 16/Dec/16 ] |
|
Hi davy, Thanks for reporting this issue. Would you please clarify whether this issue is affecting a single node or all of the nodes in your replica set? If this issue is only affecting a single node, I would recommend creating a backup of your current $dbpath, and then performing an initial sync. If this issue is affects all of the nodes, please be aware that complete data recovery may not be possible. Please upgrade to 3.0.14, which includes many bug fixes and improvements. After upgrading please rerun the --repair operation, provide the output. Additional diagnostic information should be logged ( In either case, we would like to examine some of your data files to get a better understanding of what type of corruption occurred during the power failure. So we can begin our investigation, would you please upload the following?
I've created a secure upload portal for you to use here. Files uploaded to this portal are only visible to MongoDB employees and are routinely deleted after some time. Please note that as our investigation continues, we may need to take a look at additional files. If you are able, please backup the current $dbpath in a safe location, before proceeding with additional recovery steps. Thank you for your help, |