Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-56526

Evaluate whether we can set enable 'enableDefaultWriteConcernUpdatesForInitiate' to test-only

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • v5.0
    • Repl 2021-06-14, Repl 2021-06-28

      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.

            Assignee:
            ali.mir@mongodb.com Ali Mir
            Reporter:
            ali.mir@mongodb.com Ali Mir
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: