[SERVER-19868] Clean up how we set the storage engine for replset config servers in resmoke.py for the sharding_passthrough suites Created: 11/Aug/15  Updated: 06/Dec/16  Resolved: 06/Dec/16

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Max Hirschhorn
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-19731 Make sharding_passthrough suite set u... Closed
related to SERVER-19390 Wire Read After Optime support into R... Closed
Sprint: TIG 2016-12-12
Participants:

 Description   

As part of SERVER-19390 and SERVER-19731 we added this code to override the storageEngine to be wiredTiger anytime we're launching a process with "replSet" and "configsvr" args. This shouldn't be necessary as the code to start the config servers specifies the storage engine as wiredTiger explicitly, the problem is that if you run resmoke.py with --storageEngine=mmapv1 it overrides the explicitly set storage engine config used in the sharding fixture.



 Comments   
Comment by Max Hirschhorn [ 06/Dec/16 ]

I'm closing this ticket as "Won't fix" because the current way we hardcode this logic in resmoke.py doesn't seem problematic given that we still only support running a CSRS with the WiredTiger storage engine.

Generated at Thu Feb 08 03:52:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.