[SERVER-38889] Evaluate the usefulness of convert_to_and_from_sharded.js in a shard-as-replica-set testing environment Created: 08/Jan/19  Updated: 29/Oct/23  Resolved: 15/Feb/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.0.5, 4.1.6
Fix Version/s: 4.3.3

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: [DO NOT USE] Backlog - Sharding Team
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-38894 Change tests to use replica set shard... Closed
Related
is related to SERVER-45339 Make MigrationSourceManager send _rec... Closed
Assigned Teams:
Sharding
Backwards Compatibility: Fully Compatible
Participants:

 Description   

The convert_to_and_from_sharded.js test exercises the scenario of adding a standalone shard to a cluster. The test adds the shard, moves chunks to the shard, then removes the shard, draining it completely. With the transition to shards as replica sets starting in 4.0, it may not be worth keeping this test.

Additionally, any code changes that may rely on a shard acting as a replica set may cause this test to break. Getting rid of or altering this test to conform with current supported practices will prevent future test problems.



 Comments   
Comment by Tommaso Tocci [ 15/Feb/21 ]

This was actually fixed as part SERVER-45339

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