[SERVER-56526] Evaluate whether we can set enable 'enableDefaultWriteConcernUpdatesForInitiate' to test-only Created: 30/Apr/21  Updated: 15/Jun/21  Resolved: 15/Jun/21

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

Type: Task Priority: Major - P3
Reporter: Ali Mir Assignee: Ali Mir
Resolution: Won't Do Votes: 0
Labels: pm-2130-post-rc0, post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backport Requested:
v5.0
Sprint: Repl 2021-06-14, Repl 2021-06-28
Participants:

 Description   

In SERVER-55689, we created a server parameter 'enableDefaultWriteConcernUpdatesForInitiate' that would allow us to update IDWC during reconfig. This is needed due to an optimization in our jstest infrastructure where we initiate replica sets by initiating a single node set, and then reconfig the whole membership set in. This server parameter should only ever be used by our testing infrastructure, but setting it to test-only in the IDL file caused test failures. Specifically, tests that manually disabled enableTestCommands failed because we couldn't set up a replica set test fixture, as we required setting the test-only 'enableDefaultWriteConcernUpdatesForInitiate' parameter in initiate.

 

As a result, we've omitted the test-only field from 'enableDefaultWriteConcernUpdatesForInitiate'. We should evaluate if leaving it as an undocumented server parameter would be sufficient.


Generated at Thu Feb 08 05:39:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.