[SERVER-14093] Assertion failure !e.eoo() in bsonobjbuilder.h when sorting on an empty field name Created: 30/May/14 Updated: 10/Dec/14 Resolved: 07/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.4.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jiangcheng Wu | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | Linux |
| Participants: |
| Description |
|
Got "Assertion failure !e.eoo() src/mongo/db/../bson/bsonobjbuilder.h" when queried at SECONDARY
Logs:
SECONDARY1:
|
| Comments |
| Comment by Ramon Fernandez Marina [ 07/Jul/14 ] | ||||||||||||||||||||||||||||||
|
Marking ticket as resolved, as this issue has been fixed in 2.6. | ||||||||||||||||||||||||||||||
| Comment by Jason McCay [ 03/Jul/14 ] | ||||||||||||||||||||||||||||||
|
Thomas ... thanks for the update on this. One of the customers that we support was seeing this, so I am not exactly sure what they were doing to cause it. However, they were using 2.4.x versions of MongoDB as well as Mongoid. Thanks for verifying this and showing how it is improved in 2.6. Grateful for your efforts. | ||||||||||||||||||||||||||||||
| Comment by Thomas Rueckstiess [ 30/Jun/14 ] | ||||||||||||||||||||||||||||||
|
Okay I was able to reproduce this with an empty field name (""), I think that's what you meant.
This also happens when querying on the primary node. In 2.6.x this is caught and returns an error:
| ||||||||||||||||||||||||||||||
| Comment by Thomas Rueckstiess [ 30/Jun/14 ] | ||||||||||||||||||||||||||||||
|
Hi jasonmccay, How did you construct a document that is missing a field name? What driver do you use? Regards, | ||||||||||||||||||||||||||||||
| Comment by Jason McCay [ 14/Jun/14 ] | ||||||||||||||||||||||||||||||
|
Just an observation ... but we have seen this error in the past (MongoDB 2.4.8) and it was caused by a malformed query. In our case, it was an $orderby that that was missing a field argument ... so it looked like: $orderby: { : 1 } }. | ||||||||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 03/Jun/14 ] | ||||||||||||||||||||||||||||||
|
Hi wujiangcheng, we'll need more information to try to diagnose this problem. Can you please send us the logs from the primary and the secondaries covering the last few hours leading up to this issue? Also, can you send us the full query that's triggering the issue? You may want to validate your data; be aware that this operation is resource-intensive and may have an impact on the performance of your MongoDB instance, so you may want to perform it one secondary at a time, during off-peak hours, and/or on a maintenance window. Regards, |