[SERVER-32052] Update ShardingTest to default to starting shard servers as single-node replica sets rather than standalones Created: 21/Nov/17  Updated: 30/Oct/23  Resolved: 21/Mar/18

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

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

Issue Links:
Depends
is depended on by SERVER-32672 Standalone replica set shards reject ... Closed
is depended on by SERVER-33444 Investigate the remaining tests that ... Closed
Related
related to SERVER-33599 Out collection not in UUID catalog wh... Closed
related to SERVER-33180 Update 2_test_launching_cluster.js te... Closed
related to SERVER-33597 Make allow_partial_results.js, return... Closed
related to SERVER-33601 Make sharding_migrate_large_docs.js, ... Closed
is related to SERVER-32529 Requiring replSet for shards breaks Q... Closed
is related to SERVER-32051 Require shard servers and config serv... Closed
is related to SERVER-32105 Require shard servers and config serv... Closed
is related to SERVER-32531 Require --shardsvrs not started in qu... Closed
is related to SERVER-27342 Do not block unnecessarily on connect... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-01-15, Sharding 2018-02-12, Sharding 2018-02-26, Sharding 2018-03-12
Participants:

 Description   

Since shard servers are required to be replica sets as of 3.6 (SERVER-32051), we should update our test infrastructure to always start shards as replica sets.

Note: Ensure that doing so does not significantly increase test run times (does not cause suites to time out on Evergreen).



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

Author:

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

Message: SERVER-32052 don't start servers as rs in enterprise ldap auth
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/99b712c9c32e4c0eb87cd4d78ef8423bda6bdf7c

Comment by Githook User [ 09/Mar/18 ]

Author:

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

Message: SERVER-32052 Update ShardingTest to default to starting shard servers as replica sets
Branch: master
https://github.com/mongodb/mongo/commit/da1e0304e8eb91711ea1c78eb8f62538b53680e7

Comment by Misha Tyulenev [ 05/Dec/17 ]

This change will require several changes for ShardingTest: currently known:
1) add a flag to create RS shards by default
2) make naming consistent - currently there are few hundred references to a "shard0000", "shard0001" etc. They match only standalone shard naming schema, RS shards have different names.
An easy way is to replace it with st.shard0.shardName and fix where ShardingTest instance var is named differently, however it does not work if the shard was added via addShard command

there are may be more issues down the road.

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