While dumping a database with mongodump if a collection is dropped before it was dumped, the mongodump will fail.

mongodump should be able to tolerate such failures at least with --oplog option.

Steps to reproduce:
1) Create two collections with some records.
2) Start mongodump and when it starts dumping the first collecton, suspend the process (SIGSTOP)
3) Drop the second collection
4) Resume the mongodump process (SIGCONT)

It should fail as:

writing test.c1 metadata to dump/test/c1.metadata.json
2015-12-26T18:53:09.909+1100	done dumping test.c1 (10000 documents)
2015-12-26T18:53:09.910+1100	writing test.mgendata to dump/test/mgendata.bson
2015-12-26T18:53:09.915+1100	writing test.mgendata metadata to dump/test/mgendata.metadata.json
2015-12-26T18:53:09.915+1100	Failed: error running `listIndexes`. Collection: `test.mgendata` Err: no collection