[SERVER-39811] Add a threshold of the total size of buffered oplog entries in a transaction and make it tunable, defaulting to unlimited Created: 25/Feb/19  Updated: 29/Oct/23  Resolved: 23/May/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.12

Type: Task Priority: Major - P3
Reporter: Gregory McKeon (Inactive) Assignee: Matthew Russotto
Resolution: Fixed Votes: 0
Labels: bigtxns_diagnostics
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-06-03
Participants:

 Comments   
Comment by Alyson Cabral (Inactive) [ 12/Jun/19 ]

Hi Jonathan, the Atlas team would be best to confirm the exact value with but yes, I believe they are setting this to 16MB for the free tier, giving the behavior of 4.0. 

Comment by Jonathan DeStefano [ 12/Jun/19 ]

Hi alyson.cabral, stepping in for the Atlas docs. If I'm understanding correctly, there is a 16MB transaction limit on Atlas free-tier clusters (replica sets). Mind confirming or clarifying?

Comment by Githook User [ 23/May/19 ]

Author:

{'email': 'matthew.russotto@10gen.com', 'name': 'Matthew Russotto', 'username': 'mtrussotto'}

Message: SERVER-39811 Add a threshold of the total size of buffered oplog entries in a transaction and make it tunable, defaulting to unlimited
Branch: master
https://github.com/mongodb/mongo/commit/e35e202e414df3f917ff26937f5e8325cce56b1e

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