[SERVER-33830] Fix failing tests when shards are started as replica sets Created: 12/Mar/18  Updated: 29/Oct/23  Resolved: 02/Oct/19

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

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: ShardsAsReplicaSetsInTest, open_todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-38894 Change tests to use replica set shard... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-10-21
Participants:

 Description   

The following tests fail when shard servers are started as replica sets, each for a different reason.

migrateBig_balancer.js
Fails with the error

InternalError: allocation size overflow

startup_with_all_configs_down.js
This test restarts a shard without restarting mongobridge, but when the shard is a replica set the test fails with the error

Could not find host matching read preference

The following tests need more investigation as to why they fail:
bouncing_count.js
kill_pinned_cursor.js
move_stale_mongos.js
sharded_agg_cleanup_on_error.js



 Comments   
Comment by Githook User [ 02/Oct/19 ]

Author:

{'name': 'Cheahuychou Mao', 'username': 'cheahuychou', 'email': 'cheahuychou.mao@mongodb.com'}

Message: SERVER-33830 Fix failing tests when shards are started as replica sets
Branch: master
https://github.com/mongodb/mongo/commit/aebb8ab9db04d6f675293d0739d55d6dd88c53d6

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