I installed MongoDB 2.8.0-rc1 to test with, and I did a dump with the intention of testing WiredTiger. I then did a restore and it gets OOM'd after slowly climbing up to 90%+ of available memory. I initially had a 2GB VM but I increased it to 4GB. This was also with nothing else running apart from the server.

I tried it with -j 1 to see if it made any difference and it didn't. I also started the server with the default storage engine and that made no difference either (I didn't expect it to...).

The first file it tries is files.bson (which is probably because it's the only collection which starts with a lower-case letter), which is our filesystem-in-the-database. It's by far the biggest collection but it's still only 6.3GB.

Please let me know if I can provide any more info.

I downloaded 2.6.5 to try restoring but it wouldn't restore from the same files, let me know if you want me to pursue that.

Backtrace: https://gist.github.com/mattparlane/30ea0244f2848d705c93