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

ShardedClusterFixture always starts shards as replicasets

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Linked BF Score:
      10

      Description

      Currently, if these test suites starts shards as replica sets by default,  this check in jstests/core/explain_shell_helpers.js will fail with FailedToSatisfyReadPreference. One solution is to make num_rs_nodes_per_shard default to 2. However, we should investigate why this test did not fail for standalones.

      jstests/core/read_after_optime.js should be blacklisted in this ticket because the test requires that replication is not enabled so is not expected to pass when shards are started as replica sets.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tommaso.tocci Tommaso Tocci
              Reporter:
              cheahuychou.mao Cheahuychou Mao
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: