[SERVER-7228] Mongo dump fails with BSONElement: bad type xxx Created: 02/Oct/12 Updated: 09/Jan/13 Resolved: 19/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Glen Heiberg | Assignee: | Shaun Verch |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | dump | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Running a sharded configuration of Mongo 2.2 in Amazon EC2 with 2 replica sets of 2 db nodes each, 1 arbiter for each replSet and 3 config servers. The config servers and arbiters are EC2 t1.micro instances. All servers are running: |
||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
We experience intermittent failures when doing a mongodump of our production database with errors similar to the one below: Mon Oct 1 15:30:15 Metadata for Briteblue.activities to /mnt/mongobackup/Briteblue/activities.metadata.json Some observations: Oddly, doing a mongodump with the 2.0.7 binary against the very same 2.2 database works perfectly (as does the restore using mongorestore 2.2) Running db.collection.validate() shows no errors for any of the collections. |
| Comments |
| Comment by Shaun Verch [ 18/Oct/12 ] |
|
Hi Glen, It's looking like If so, could you do the following? Next time a mongodump fails, could you log into the mongod that it failed on, increase the log level (http://docs.mongodb.org/manual/reference/command/setParameter/), run mongodump again, and send us the logs from the mongod itself? Even the logs from the last time this failed would be helpful (if you still have the log from around Mon Oct 1 15:30:15). Thanks! |
| Comment by Shaun Verch [ 04/Oct/12 ] |
|
Thank you for the report. We are looking into this issue, and will let you know if we need any additional information. |