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

Change replica set fixture used by replica_sets_jscore_passthrough to make its secondary have zero votes

    • Fully Compatible
    • v3.6, v3.4, v3.2
    • TIG 2018-1-15
    • 0

      To prevent unexpected failovers due to machine slowness. We could apply this to any passthrough suites that run against a replica set and expect a stable topology for the duration of the test.

      This changes the suites meeting the criteria:

      1. uses a ReplicaSetFixture or ShardedClusterFixture (which uses a ReplicaSetFixture)
      2. has more than one node in the replica set
      3. does not specify voting_secondaries: true
      4. does not specify all_nodes_electable: true

      Namely, these suites:

      • aggregation_read_concern_majority_passthrough
      • integration_tests_replset
      • jstestfuzz_replication
      • jstestfuzz_replication_initsync
      • jstestfuzz_replication_resync
      • jstestfuzz_replication_session
      • read_concern_linearizable_passthrough
      • read_concern_majority_passthrough
      • replica_sets_initsync_jscore_passthrough
      • replica_sets_initsync_static_jscore_passthrough
      • replica_sets_jscore_passthrough
      • replica_sets_resync_static_jscore_passthrough
      • retryable_writes_jscore_passthrough
      • change_streams_secondary_reads
      • jstestfuzz_sharded_continuous_stepdown

            kevin.albertson@mongodb.com Kevin Albertson
            spencer@mongodb.com Spencer Brody (Inactive)
            0 Vote for this issue
            6 Start watching this issue