Investigate the remaining tests that fail when shard servers are started as replica sets

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.4
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2018-03-12, Sharding 2018-03-26, Sharding 2018-04-09
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      ShardingTest now defaults to starting shard servers as replica sets as of SERVER-32052. The following tests fail when shard servers are started as replica sets and the failures need further investigation. Currently, these tests are still being started as standalones, and we should convert them to being started as replica sets.

      sharding_migrate_large_docs.js
      read_only_tests.js
      allow_partial_results.js
      basic_sharding_params.js
      bulk_insert.js
      bouncing_count.js
      cursor_timeout.js
      forget_mr_temp_ns.js
      kill_pinned_cursor.js
      mapReduce_outSharded.js
      migrateBig_balancer.js
      min_optime_recovery_on_failed_move_chunk_commit.js
      move_stale_mongos.js
      movechunk_with_moveParanoia.js
      mr_noscripting.js
      mrShardedOutput.js
      prefix_shard_key.js
      return_partial_shards_down.js
      startup_with_configs_down.js
      write_commands_sharding_state.js

            Assignee:
            Janna Golden
            Reporter:
            Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: