[SERVER-5755] Invalid BSONObj size: ... 0xEEEEEEEE when deleting Created: 03/May/12 Updated: 15/Aug/12 Resolved: 09/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aristarkh Zagorodnikov | Assignee: | Tad Marshall |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | corrupt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Recently, we 've started getting the following assertions in log file when trying to delete documents (not on every delete, it happens occasionally, about 1 in a million documents deleted): Thu May 3 13:09:39 [conn567441] Assertion: 10334:Invalid BSONObj size: -286331154 (0xEEEEEEEE) first element: _id: { F: 23866263275 29652228, C: 2, i: 288230376151857194, u: 288230376151872074 }0x584102 0x508521 0x93df93 0x88ca07 0x88e8e0 0xaa33f6 0x637407 0x7f627b6669ca 0x7f627ac1570d The record with the mentioned _id is not to be found in the collection (we are not sure if was deleted or wasn't there before in the first place). |
| Comments |
| Comment by Aristarkh Zagorodnikov [ 09/May/12 ] |
|
Well, I guess 2.2 is a bit far for us to wait for, but it's good to know it might be already fixed, looking forward to 2.2 release. |
| Comment by Tad Marshall [ 09/May/12 ] |
|
Great, thanks for letting us know! Re: "I hope that index won't get into this condition by itself though =)": Here is one case we've identified that can result in index corruption: https://jira.mongodb.org/browse/SERVER-5552 . This is currently scheduled to get fixed in 2.1.2 so hopefully we can avoid making you reindex in the future. |
| Comment by Aristarkh Zagorodnikov [ 09/May/12 ] |
|
Sorry for the delay, reindexing helped and the assert is gone for now. |
| Comment by Aristarkh Zagorodnikov [ 03/May/12 ] |
|
Reindexing would take some time for this db (it contains around 140 million records), I'll report later. |
| Comment by Aristarkh Zagorodnikov [ 03/May/12 ] |
|
Thanks for the info, we'll try rebuilding index. I hope that index won't get into this condition by itself though =) |
| Comment by Tad Marshall [ 03/May/12 ] |
|
This usually indicates a stale entry in the index that is being used. A deleted record remains in the index and the "Assertion: 10334:Invalid BSONObj size: -286331154 (0xEEEEEEEE)" is triggered when the code looks at the (no longer present) document. It does not indicate corruption in the data itself. Rebuilding the index should make the assertions stop. |