[SERVER-66625] SingleServerDiscoveryMonitor::requestImmediateCheck can be ignored Created: 20/May/22 Updated: 12/Dec/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | 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
|
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 43 | ||||||||||||
| Story Points: | 4 | ||||||||||||
| Description |
|
for a long time due to outstanding hello request. There is currently a throttling mechanism to prevent the monitor from refreshing too frequently. However, in the case when the outstanding request is taking too long (for example, in one of our tests, we discard network messages), this can cause the monitor to not try to refresh even though the destination becomes healthy. Note that for streamable hello, it has a minimum 10 sec timeout, whereas single hello uses a different timeout. |