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
- depends on
-
SERVER-32052 Update ShardingTest to default to starting shard servers as single-node replica sets rather than standalones
- Closed