[SERVER-4291] Assertion: 13273:single data buffer expected while using mongodump Created: 15/Nov/11  Updated: 11/Jul/16  Resolved: 18/Nov/11

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 2.0.1
Fix Version/s: 2.0.7, 2.1.0

Type: Bug Priority: Major - P3
Reporter: Myers Carpenter Assignee: Tad Marshall
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

64 bit server, 32 bit client.


Operating System: ALL
Participants:

 Description   

$ mongodump --host xxxx --username xxxx --password xxx --collection xxx --db xxxx
connected to: prodmongoperf-a.lan.flt
DATABASE: locos_production       to     dump/locos_production
        locos_production.conversations.user_history.encounters to dump/locos_production/conversations.user_history.encounters.bson
                12800/3595618   0%
                32100/3595618   0%
                50600/3595618   1%
^[              69000/3595618   1%
                86400/3595618   2%
                103900/3595618  2%
                127200/3595618  3%
                144700/3595618  4%
                162200/3595618  4%
                179700/3595618  4%
                197200/3595618  5%
                214700/3595618  5%
                238000/3595618  6%
                255400/3595618  7%
                278800/3595618  7%
                290400/3595618  8%
                302100/3595618  8%
Tue Nov 15 16:23:21 Assertion: 13273:single data buffer expected
0x81b22f5 0x820fa68 0x8211c58 0x81ef9f8 0x81f007f 0x8707709 0x8708293 0x870c470 0x870e738 0x8701231 0x8706c99 0xb7447bd6 0x8128e91
 mongodump(_ZN5mongo11msgassertedEiPKc+0x145) [0x81b22f5]
 mongodump(_ZN5mongo14DBClientCursor12dataReceivedERbRSs+0x198) [0x820fa68]
 mongodump(_ZN5mongo14DBClientCursor18exhaustReceiveMoreEv+0x178) [0x8211c58]
 mongodump(_ZN5mongo18DBClientConnection5queryEN5boost8functionIFvRNS_27DBClientCursorBatchIteratorEEEERKSsNS_5QueryEPKNS_7BSONObjEi+0x1d8) [0x81ef9f8]
 mongodump(_ZN5mongo18DBClientConnection5queryEN5boost8functionIFvRKNS_7BSONObjEEEERKSsNS_5QueryEPS4_i+0x43f) [0x81f007f]
 mongodump(_ZN4Dump12doCollectionESsP8_IO_FILEPN5mongo13ProgressMeterE+0x459) [0x8707709]
 mongodump(_ZN4Dump19writeCollectionFileESsN5boost10filesystem10basic_pathISsNS1_11path_traitsEEE+0x1b3) [0x8708293]
 mongodump(_ZN4Dump2goESsN5boost10filesystem10basic_pathISsNS1_11path_traitsEEE+0x480) [0x870c470]
 mongodump(_ZN4Dump3runEv+0x1b38) [0x870e738]
 mongodump(_ZN5mongo4Tool4mainEiPPc+0x1631) [0x8701231]
 mongodump(main+0x59) [0x8706c99]
 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6) [0xb7447bd6]
 mongodump() [0x8128e91]
assertion: 13273 single data buffer expected
Tue Nov 15 16:23:21 Socket flush send() errno:9 Bad file descriptor 10.130.161.82:27017
Tue Nov 15 16:23:21   caught exception (socket exception) in destructor (~PiggyBackData)



 Comments   
Comment by Tad Marshall [ 22/Jun/12 ]

Backported to 2.0.7.

Comment by auto [ 22/Jun/12 ]

Author:

{u'date': u'2012-06-22T09:04:22-07:00', u'email': u'brandon@10gen.com', u'name': u'Brandon Diamond'}

Message: SERVER-4291: Return code of recv unchecked

Signed-off-by: Tad Marshall <tad@10gen.com>
Branch: v2.0
https://github.com/mongodb/mongo/commit/4bb6e76b20a3f8fd49fb4677b189b41088f3a962

Comment by Tad Marshall [ 22/Jun/12 ]

Marked for backport to 2.0.7.

Comment by Daniel Pasette (Inactive) [ 07/Jun/12 ]

@Jerome: This was indeed fixed for 2.1.0, but the ticket was not marked correctly with the fixVersion or with backport yes. Thanks for bringing to our attention.

Comment by Jérôme Petazzoni [ 07/Jun/12 ]

I had the same issue with MongoDB 2.0.2. The initial synchronization of a 8 GB replica set would never complete. It would reach a given point, then crash, and restart, and repeat the whole loop endlessly.

I rebuilt mongod 2.0.2 (cherry-picking https://github.com/mongodb/mongo/commit/d28c919025766e7a61904fb39b6ebea6d65ba502) and this time the resynchronization was successful.

It looks like this patch was already applied in the 2.1 series, but not to the latest 2.0 series (2.0.6 to date). IMHO, it would make a lot of sense to backport it to the next 2.0 release.

Comment by Brandon Diamond [ 17/Nov/11 ]

Added a check to ensure data was received successfully. Are you able to reproduce this issue? If so, can you try to reproduce with the above commit?

Comment by auto [ 17/Nov/11 ]

Author:

{u'login': u'', u'name': u'Brandon Diamond', u'email': u'brandon@10gen.com'}

Message: SERVER-4291: Return code of recv unchecked
Branch: master
https://github.com/mongodb/mongo/commit/d28c919025766e7a61904fb39b6ebea6d65ba502

Generated at Thu Feb 08 03:05:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.