[SERVER-8227] Assertion in mongo log: 10334:Invalid BSONObj size: 1769280243 (0xF3127569) first element: : ?type=100 Created: 18/Jan/13 Updated: 10/Dec/14 Resolved: 04/Apr/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.2.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dmitry Chernikov | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 1 |
| Labels: | bson, crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS, x86_64, |
||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
We have 6 servers in replica set, accessed using C++ and python drivers. mongo.log Thu Jan 17 11:00:43 [conn103] Assertion: 10334:Invalid BSONObj size: 1769280243 (0xF3127569) first element: : ?type=100 /usr/bin/mongod(_ZNK5mongo3Mod5applyERNS_15BSONBuilderBaseENS_11BSONElementERNS_8ModStateE+0x191b) [0x84c46b] /usr/bin/mongod(_ZN5mongo11ModSetState17createNewFromModsERKSsRNS_15BSONBuilderBaseERNS_18BSONIteratorSortedERKSt4pairIKSt17_Rb_tree_iteratorIS7_IS1_N5boost10shared_ptrINS_8ModStateEEEEESF_ERKNS_9LexNumCmpE+0x4dd) /usr/bin/mongod(_ZN5mongo11ModSetState20createNewObjFromModsERKSsRNS_14BSONObjBuilderERKNS_7BSONObjE+0x7f) [0x85145f] /usr/bin/mongod(_ZN5mongo14_updateObjectsEbPKcRKNS_7BSONObjES4_bbbRNS_7OpDebugEPNS_11RemoveSaverEbRKNS_24QueryPlanSelectionPolicyEb+0x3081) [0x841fc1] /usr/bin/mongod(_ZN5mongo13updateObjectsEPKcRKNS_7BSONObjES4_bbbRNS_7OpDebugEbRKNS_24QueryPlanSelectionPolicyE+0xb7) [0x844a27] /usr/bin/mongod(_ZN5mongo14receivedUpdateERNS_7MessageERNS_5CurOpE+0x4cf) [0x7ade1f] /usr/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0xbd4) [0x7b4284] /usr/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x82) [0x5703f2] /usr/bin/mongod(_ZNK5mongo7BSONObj8toStringERNS_17StringBuilderImplINS_16TrivialAllocatorEEEbbi+0x317) [0x5745c7] /usr/bin/mongod(_ZNK5mongo11BSONElement8toStringERNS_17StringBuilderImplINS_16TrivialAllocatorEEEbbi+0x69b) [0x572fdb] /usr/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x43b) [0x7b3aeb] /usr/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x82) [0x5703f2] We tracked down to piece of code which causes this, but it consists of 3 queries within single connections: schematic code conn->insert( "collTickets", ticketObj ); objects sizes are guaranteed to be much less than 16MB:
What can cause this assertion failures? |
| Comments |
| Comment by kuku [ 28/May/13 ] |
|
ue May 28 18:09:31 [conn396] Assertion: 10334:Invalid BSONObj size: -286331391 (0x01EEEEEE) first element: : ?type=112 Ask for help, every day, Thinks! |
| Comment by James Wahlin [ 07/Mar/13 ] |
|
Hi Alexander, From the log trace above it looks like the BSON object itself is invalid. The "first element:" trace shows "?type=100" where 100 is not a valid BSON type. MongoDB code prepends a ? when an unknown type is encountered in this path. You can find the code here: My first question to you is what version of the C++ driver are you running? If older than 2.2.2 I would suggest upgrading. If you are running the 2.2.2 client then we will need to dive deeper. The path above appears to be triggered by an update so at this point it is not clear whether the driver is generating invalid BSON or whether the update path is generating. Thanks, |
| Comment by Alexander Borodetsky [ 18/Jan/13 ] |
|
Also we have MMS account associated with my JIRA account. This issue occured on repset "wop" |
| Comment by Alexander Borodetsky [ 18/Jan/13 ] |
|
Also i want to underline - this is not |
| Comment by Alexander Borodetsky [ 18/Jan/13 ] |
|
Please change "Affects Version/s" to 2.2.2 as well. Because actually it is happens on 2.2.2 NOT on 2.2.0 |
| Comment by Dmitry Chernikov [ 18/Jan/13 ] |
|
forgot to mention that we use a version of mongod 2.2.2, |