Info

zbigMapReduce.js can roll over its oplog if the inserts go fast enough and the fetching is a bit slow, leading to unrecoverable rollbacks. Reducing the data size to 50MB total or increasing the oplog size to 250 MB (or something in the middle) would be good.

Top User Comments

xgen-internal-githook commented on Thu, 19 Jan 2017 22:35:38 +0000: Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'} Message: SERVER-27409 Ensure zBigMapReduce.js does not roll over oplog with write concern (cherry picked from commit 77f9f8c05e37a73a1195ef16185ed5c2ec5e7f6c) Branch: v3.4 https://github.com/mongodb/mongo/commit/9af9840664bc7b892c1c017db31b086bf0ea9bf9 xgen-internal-githook commented on Tue, 17 Jan 2017 20:57:57 +0000: Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'} Message: SERVER-27409 Ensure zBigMapReduce.js does not roll over oplog with write concern Branch: master https://github.com/mongodb/mongo/commit/77f9f8c05e37a73a1195ef16185ed5c2ec5e7f6c judah.schvimer commented on Thu, 22 Dec 2016 17:23:14 +0000: Given the current issues with this test getting OOM killed, reducing the number of inserted documents may be the better solution.

Steps to Reproduce