[SERVER-77146] Verify checkConfigVersionDoc function is successful in jstest Created: 15/May/23 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kruti Shah | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Cluster Scalability
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 4 | ||||
| Story Points: | 1 | ||||
| Description |
|
After investigating the Bf, the timeout expired by the server is most likely the time it took for the OS and our networking stack to notice that the previous connections were closed and bubble the error up the stack. The fix for the jstest/multiVersion/genericSetFCVUsage/upgrade_downgrade_sharded_cluster.js test would be to make sure checkConfigVersionDoc function in the test is robust to the server being restarted. |