[SERVER-32888] Set a default oplog size for replica sets started by resmoke.py Created: 25/Jan/18  Updated: 30/Oct/23  Resolved: 14/Feb/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.7.3

Type: Improvement Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Eddie Louie
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-27843 Reduce oplog size for read_concern_li... Closed
Backwards Compatibility: Fully Compatible
Sprint: TIG 2018-02-26
Participants:
Linked BF Score: 0

 Description   

We don't currently do this and it means that each mongod will consider 5% of the avaiable disk space as its default oplog size. Other than SERVER-27843, this seemingly hasn't been an issue in Evergreen. I believe this is because when we aren't setting the oplog size in the resmoke.py YAML suite, we are either (a) running with WiredTiger and taking advantage of disk compression, or (b) running with MMAPv1 but only using --jobs=1.

I think we should use a 511MB oplog as the default in ReplicaSetFixture to match what we're already doing in the replica_sets_jscore_passthrough.yml test suite. I suspect that if we were to try and match the 40MB oplog of ReplSetTest for data members or the 16MB oplog of ShardingTest replica set shards, then we'd end up making the work from SERVER-26884 less useful because a smaller oplog would retain less history.



 Comments   
Comment by Githook User [ 14/Feb/18 ]

Author:

{'email': 'eddie.louie@mongodb.com', 'name': 'Eddie Louie', 'username': 'elouie99'}

Message: SERVER-32888 Set a default oplog size for replica sets started by resmoke.py
Branch: master
https://github.com/mongodb/mongo/commit/8865f48da84e0864ddd21f64f067bce5868345c2

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