[SERVER-43892] ShardedClusterFixture always starts shards as replicasets Created: 08/Oct/19 Updated: 29/Oct/23 Resolved: 24/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 10 | ||||||||||||||||||||
| Description |
|
Currently, if these test suites starts shards as replica sets by default, this check in jstests/core/explain_shell_helpers.js will fail with FailedToSatisfyReadPreference. One solution is to make num_rs_nodes_per_shard default to 2. However, we should investigate why this test did not fail for standalones. jstests/core/read_after_optime.js should be blacklisted in this ticket because the test requires that replication is not enabled so is not expected to pass when shards are started as replica sets. |
| Comments |
| Comment by Githook User [ 24/Feb/21 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |