Mongodb import interrupt

  mongodb, question
2017-11-10T15:14:59.925+0800    [##......................]    bs.operationHistory   11.7MB/136MB  (8.5%)
 2017-11-10T15:14:59.925+0800    [........................]             bs.sendSms   3.16MB/128MB  (2.5%)
 2017-11-10T15:14:59.925+0800    [#.......................]  bs.topicData_wellness  3.70MB/58.3MB  (6.4%)
 2017-11-10T15:14:59.925+0800    [#.......................]      bs.topicData_test  3.27MB/43.8MB  (7.5%)
 2017-11-10T15:14:59.925+0800
 2017-11-10T15:14:59.940+0800    [#.......................]  bs.topicData_wellness  3.70MB/58.3MB  (6.4%)
 2017-11-10T15:14:59.940+0800    Failed: bs.topicData_wellness: error restoring from bs/topicData_wellness.bson: insertion error: EOF

As above, there are always import errors. What is this problem?
The data source is version 2.4 library, now import version 3.x, is this the problem?

Another question and answer …
First of all, I agree with MONGOING’s answer above. Different versions of MONGO will have problems in the interpretation of bson …
Although this bson analysis problem was encountered, the screenshots were not released, so thank you upstairs for adding this note.
The reason for the failure of this import was finally solved by opening swap, so I think the most likely cause of this problem is that vps does not have enough memory, resulting in bson not being able to resolve it on a large scale.
The problem was successfully imported after swap 2Gb was opened. Strangely, there was no bson parsing error. I think the new version is compatible.