[SERVER-33444] Investigate the remaining tests that fail when shard servers are started as replica sets Created: 22/Feb/18  Updated: 29/Oct/23  Resolved: 27/Mar/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-32052 Update ShardingTest to default to sta... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-03-12, Sharding 2018-03-26, Sharding 2018-04-09
Participants:

 Description   

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



 Comments   
Comment by Githook User [ 27/Mar/18 ]

Author:

{'email': 'golden.janna@gmail.com', 'name': 'jannaerin', 'username': 'jannaerin'}

Message: SERVER-33444 Fix tests that fail when shard servers started as replica sets
Branch: master
https://github.com/mongodb/mongo/commit/a13de396ad866e677cb6e9598852b1f84e6b8346

Generated at Thu Feb 08 04:33:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.