[SERVER-54628] Make hedging_metrics_server_status.js determistic Created: 19/Feb/21 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-wfbf-sprint | ||
| 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: | 10 | ||||
| Description |
|
This test relies on failpoints to simulate an advantageously hedged read request. However, based on this BF-19852, the test setup still does not guarantee that the response for the original request always arrives after the response for the hedged/additional request does. The quick fix to increase the blockTimeMS for the original request. However, unless we use a large blockTimeMS, there is a non-zero chance that we get a similar BF in the future. So we might need to rewrite this test to not rely on failpoints. |