[SERVER-17018] Assertion failure false src/mongo/db/structure/btree/key.cpp 433 on remove operation Created: 23/Jan/15 Updated: 04/Jun/15 Resolved: 06/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.6.9 |
| Fix Version/s: | 2.6.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yuki Okamoto | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS: Windows Server 2008 R2 Standard SP1 64bit |
||
| Attachments: |
|
|
| Backwards Compatibility: | Fully Compatible | |
| Operating System: | Windows | |
| Steps To Reproduce: |
|
|
| Participants: |
| Description |
|
I got this assertion error when execute remove operation. After doing procedure(refer to "Steps To Reproduce"), you can find the error log like below.
Frequency of occurrence is:
I attached the tool written above:
This tool means: I think the important point to occur this error is to execute index scan stage in remove operation by setting "two" items in remove operation's query.
(setting two items : "_id" and "key") |
| Comments |
| Comment by Yifeng Zhou [ 12/May/15 ] |
|
Hi Ramon, I appreciate your reply. I understood 3.0.x versions are not affected by this issue. |
| Comment by Ramon Fernandez Marina [ 11/May/15 ] |
|
zhouyifeng, as per my earlier comment we were unable to reproduce the issue in 3.0.2, so the 3.0.x versions should not be affected by this issue. Update |
| Comment by Yifeng Zhou [ 11/May/15 ] |
|
I'm a coworker of Yuki Okamoto. Thank you for update patch. We will test the effect in 2.6.x. |
| Comment by Githook User [ 06/May/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |
| Comment by Ramon Fernandez Marina [ 29/Apr/15 ] |
|
y-okamoto, I'm able to reproduce the behavior you describe on the 2.6 series (tried 2.6.7 and 2.6.9), but so far not on 3.0.2. It is possible that this issue was fixed as part of the work that went into the 3.0 series, so would it be possible for you to test with 3.0.2? We'll investigate the issue in 2.6, but if you're evaluating MongoDB for a new installation I'd recommend you consider 3.0.2 anyway. Thanks, |
| Comment by Yuki Okamoto [ 27/Apr/15 ] |
|
Thank you for trying reproducing this issue. reproduction.zip ・testTenant0.0 — testTenant0.ns ・validate.txt ・mongo.log In validate.txt, "nrecords" should be "1000000" but it's "1000002". Environment: Regards, |
| Comment by Sam Kleinman (Inactive) [ 08/Apr/15 ] |
|
Thanks for this report. I'm working on reproducing this issue, but haven't yet hit this assertion. Assertions in this part code are often related to data integrity. To continue to debug this issue, it would be very helpful if we could get a copy of your data files that you have run into this issue with. Also consider running validate() on the affected collections and check the underlying storage devices and disks. Thanks for your patience and I hope we can get to the bottom of this soon. Regards, |