I am currently updating our database to Mongo 3.0, and I am in the stage of updating our daily backup process using mongodump from 2.6.1 to 3.0.1, which has great performance due to the parallel collection .
I ran into a problem when mongodump fails halfway with an error
....
2015-04-10T00:42:54.606+0000 [
2015-04-10T00:42:57.352+0000 Failed: error reading collection: Closed explicitly.
Of the 8 attempts, 6 of them failed, and 2 of them went through a fine. I could not find anything else on the Internet about this particular error.
- The entire mongodump is about 1 TB, with thousands of collections. The crash happens somewhere in the middle. Mongodump really starts as many files
.bsonstart to accumulate on disk and I can see progress files on mongodump output- When running the same code with an instance of mongo 2.4 with a frequency of 150 GB, it seems to work fine, it probably doesn't work long enough to make the error.
- The mongo database version with which I am resetting is 2.4, we plan to update 2.4 → 2.6 → 3.0. Therefore, we wanted to update the mongodump tool in advance, hoping that it would work perfectly with 2.4 and 2.6.
- Existing backup servers use mongodump 2.6.1 for 2.4 mongo databases, and they hum good, 100% reliability from the mongodump stage of the backup pipeline
mongodump ( Google) mongo (hard metal server), mongo . , SSH- , mongodump --port. :
ssh -M -N -L 1234:localhost:27017 <remote_ip>
mongodump --port 1234 --username XXX --password XXX --out /tmp/dir
- , ? mongodump 3.0, mongo 3.0.
: , ,
2015-04-14T22:56:37.939+0000 Failed: error reading collection: read tcp XXX.X.X.X:XXXXX: use of closed network connection