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

Connection timeout does not cause origin to be marked down #11907

Open
vuori opened this issue Dec 11, 2024 · 0 comments
Open

Connection timeout does not cause origin to be marked down #11907

vuori opened this issue Dec 11, 2024 · 0 comments
Assignees

Comments

@vuori
Copy link

vuori commented Dec 11, 2024

As far as I understand from the documentation, hosts that are unresponsive are supposed to be marked as "down" in hostdb and retried according to the connect_attempts_max_retries_down_server setting. However with the following steps this does not seem to be happening:

  1. Attempt to make a forward-proxied request to a host that is not responding at all (error is ETIMEDOUT).
  2. Note in trace log that connect_attempts_max_retries attempts are made.
  3. Try the same request again.
  4. connect_attempts_max_retries attempts are still made, the count never goes down to connect_attempts_max_retries_down_server.

In particular if the latter is set to 0, ATS still always tries to connect and the trace message Not connecting to the server because it is marked down from HttpSM.cc never appears.

Is this a bug or am I misunderstanding how hostdb is supposed to work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants