[SERVER-49484] Remove sharding_last_stable_mongos_and_mixed_shards Created: 13/Jul/20 Updated: 06/Dec/22 Resolved: 03/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
The sharding_multiversion suite's coverage is strictly greater than sharding_last_stable_mongos_and_mixed_shards. The sharding_last_stable_mongos_and_mixed_shards suite uses mixed versions for the shards, but all the replica set members in a single shard have the same version. The sharding_multiversion suite has different versions within a single shard. One reason to keep the suite is since sharding_last_stable_mongos_and_mixed_shards chooses binary versions deterministically, it will fail more consistently. |
| Comments |
| Comment by Kaloian Manassiev [ 04/Sep/20 ] |
|
We decided to close this as "Won't Fix" exactly because of the last consideration that you listed, Tess: "One reason to keep the suite is since sharding_last_stable_mongos_and_mixed_shards chooses binary versions deterministically, it will fail more consistently". |