Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix infra-keep-probing for low infra-cache-max-rtt values #1241

Merged
merged 1 commit into from
Feb 19, 2025

Conversation

gthess
Copy link
Member

@gthess gthess commented Feb 19, 2025

The maximum value of a probe rto was not aligned with the (configurable) infra-cache-max-rtt value. That could result in infra-keep-probing not working if an infra-cache-max-rtt value was chosen that was below 12000 ms.

This fix still uses a default value of 12000 ms for the probe but caps it to the infra-cache-max-rtt if that is lower.

  (configurable) infra-cache-max-rtt value. That could result in
  infra-keep-probing not working if an infra-cache-max-rtt value was chosen
  that was below 12000 ms. This fix still uses a default value of 12000
  ms for the probe but caps it to the infra-cache-max-rtt if that is
  lower.
@gthess gthess requested a review from wcawijngaards February 19, 2025 11:25
@gthess gthess self-assigned this Feb 19, 2025
Copy link
Member

@wcawijngaards wcawijngaards left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For those low values of rtt, the probe continuation is fairly nice to have. The code looks nice, expanded with a unit test.

@gthess gthess merged commit edb20a2 into master Feb 19, 2025
1 check passed
@gthess gthess deleted the bugfix/keep-probing-max-rtt branch February 19, 2025 12:44
gthess added a commit that referenced this pull request Feb 19, 2025
- Merge #1241: Fix infra-keep-probing for low infra-cache-max-rtt
  values.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants