[SERVER-27409] zbigMapReduce.js should use a write concern for inserts so it does not roll over its oplog Created: 13/Dec/16  Updated: 05/Apr/17  Resolved: 17/Jan/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.2, 3.5.2

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4
Sprint: Repl 2017-02-13
Participants:
Linked BF Score: 15

 Description   

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.



 Comments   
Comment by Githook User [ 19/Jan/17 ]

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

Comment by Githook User [ 17/Jan/17 ]

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

Comment by Judah Schvimer [ 22/Dec/16 ]

Given the current issues with this test getting OOM killed, reducing the number of inserted documents may be the better solution.

Generated at Thu Feb 08 04:15:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.