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

Long timeouts unintuitive behaviour #5834

Closed
pierresouchay opened this issue May 13, 2019 · 1 comment
Closed

Long timeouts unintuitive behaviour #5834

pierresouchay opened this issue May 13, 2019 · 1 comment
Labels
theme/operator-usability Replaces UX. Anything related to making things easier for the practitioner type/enhancement Proposed improvement or new feature

Comments

@pierresouchay
Copy link
Contributor

Overview of the Issue

Handling of timeouts in checks is counter-intuitive in Consul.

Consider this example:

Checks: [
 {
   "http": "http://localhost:80/healthz",
   "interval": "30s",
   "timeout": "30s"
  }
]

=> Will create a HTTP check with timeout of 10s

While:

Checks: [
 {
   "http": "http://localhost:80/healthz",
   "interval": "30s",
   "timeout": "29s"
  }
]

=> Will create a HTTP check with timeout of 29s

While I see the point of setting the timeout to interval at maximum, in that case, it should behave as an upper boudary.

I thus propose the following:

if timeout ≥ Interval => use Interval and display a Warning at registration time

pierresouchay added a commit to pierresouchay/consul that referenced this issue May 13, 2019
…ixes hashicorp#5834

When Timeouts were greater or equal than interval for checks,
Consul used to set timeout to 10s. Now, use the interval as upper
boundary in that case.

Also outputs a warning in logs in that case
@pearkes pearkes added type/enhancement Proposed improvement or new feature theme/operator-usability Replaces UX. Anything related to making things easier for the practitioner labels May 15, 2019
@s-mang
Copy link
Contributor

s-mang commented Jul 17, 2019

Closing this. Fix (#6094) is in 1.6 release branch and will go out with the 1.6 release.

@s-mang s-mang closed this as completed Jul 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme/operator-usability Replaces UX. Anything related to making things easier for the practitioner type/enhancement Proposed improvement or new feature
Projects
None yet
Development

No branches or pull requests

3 participants