[SERVER-54632] Increase number of CSRS nodes in jstests/sharding/query/json_schema.js Created: 19/Feb/21 Updated: 29/Oct/23 Resolved: 14/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Simon Gratzer (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-csrs-stepdown-upkeep | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding EMEA 2021-05-17 | ||||
| Participants: | |||||
| Linked BF Score: | 26 | ||||
| Description |
|
[Test-only issue, low priority] The test currently initializes a CSRS with one node and then performs operations that can potentially hit the ReplicaSetMonitorInterface::kDefaultFindHostTimeout of 15 seconds: it can happen that a config server stepdown + election requires more than that time. |
| Comments |
| Comment by Githook User [ 13/May/21 ] |
|
Author: {'name': 'Simon Graetzer', 'email': 'simon.gratzer@mongodb.com'}Message: |
| Comment by Kaloian Manassiev [ 19/Feb/21 ] |
|
Just to clarify: I think don't we should (directly) increase the number of nodes, but rather remove the config:1 option to ShardingTest so that the test framework can decide what number to use (which currently happens to be 3). As part of this ticket we should also audit the rest of the tests in case there are other, which hardcode the number of config server nodes. |