[SERVER-73847] add support for ReplSetTest nodeOptions in RollbackTest Created: 09/Feb/23  Updated: 29/Oct/23  Resolved: 10/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
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-31409 Create basic multi-version rollback J... Closed
is related to SERVER-70905 handle multi-oplog batched writes dur... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2023-02-20
Participants:

 Description   

The RollbackTestFixture (and RollBackTestFixtureDeluxe) supports passing in an optional ReplSetTest fixture. This requires the caller to provide a fully initialized ReplSetTest instance that meets the requirements of the RollbackTest fixture.

In some scenarios, we may want to simply add a startup parameter to the default replica set provided by performStandardSetup() without reproducing the entire default configuration. It would be convenient to be able to pass in an initial nodeOptions that would be used by performStandardSetup().



 Comments   
Comment by Githook User [ 10/Feb/23 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-73847 large batched writes rollback test provides nodeOptions to fixture
Branch: master
https://github.com/mongodb/mongo/commit/53478bd7dce5f14708fb35db41293df1ea79db33

Comment by Githook User [ 09/Feb/23 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-73847 RollbackTest accepts optional nodeOptions for ReplSetTest initialization
Branch: master
https://github.com/mongodb/mongo/commit/bb6f218ecc187c3ad5496f0e7b6ba92c621b71d0

Comment by Benety Goh [ 09/Feb/23 ]

We added support for an external ReplSetTest option in SERVER-31409.

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