[SERVER-14383] Mongodump Error : assertion: 16465 recv failed while exhausting cursor Created: 28/Jun/14 Updated: 16/Nov/21 Resolved: 03/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Replication, Sharding |
| Affects Version/s: | 2.4.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sridhara Huchappa | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | trying to run mongodump on a 800 GB collection mongodump -u <UID> -p <PWD> --authenticationDatabase admin -o /data/bak/ |
| Participants: |
| Description |
|
Sat Jun 28 05:26:36.777 Collection File Writing Progress: 7694300/12192615 63% (objects) |
| Comments |
| Comment by Thomas Rueckstiess [ 03/Jul/14 ] | ||||||||||||||||||||||||||||
|
Hi Sridhara, The log file you attached doesn't cover the the time of the initial failure of mongodump (Sat Jun 28 05:26:43.900), so I can't say for sure what the problem was. It only covers:
I noticed that the server shuts down uncleanly at Sat Jun 28 22:27:45.404, see below. On restart, the node had to recover from the journal to get into consistent state again. Is that the point when the mongodump failed? I can't tell why the server was shut down, but that would explain the "recv" error you were seeing.
It sounds like you just want to get your broken secondary up and running again with a copy of the primary. You cannot use mongodump for this, as it won't dump the local database. You can just start the secondary without the data and let it do an initial resync. To speed up the process, you can also copy the entire dbpath content over from the primary to the secondary to bootstrap the resync. For that to work, you either need to use a filesystem snapshot (LVM) or stop writes to the primary during the copy, as you would otherwise get an inconsistent copy. As I don't see any evidence for a bug here, and the SERVER project is for reporting bugs and feature requests, I'm closing this ticket as "Works as Designed". If you need further support, you can post your question on the mongodb-users group (http://groups.google.com/group/mongodb-user). Regards, | ||||||||||||||||||||||||||||
| Comment by Sridhara Huchappa [ 01/Jul/14 ] | ||||||||||||||||||||||||||||
|
Hi Thomas, Thanks for the quick response. Sorry for replying late. Attached, please see the mongo logs. The dump size is around 800GB. Regards, | ||||||||||||||||||||||||||||
| Comment by Thomas Rueckstiess [ 30/Jun/14 ] | ||||||||||||||||||||||||||||
|
Hi Sridhara, Can you please provide the full log file of the mongod you tried to dump the data from? Ideally from the time the mongodump started. Also, is this a reoccurring problem or was it just that once? Thanks, |