You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Attempt to make a forward-proxied request to a host that is not responding at all (error is ETIMEDOUT).
Note in trace log that connect_attempts_max_retries attempts are made.
Try the same request again.
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?
The text was updated successfully, but these errors were encountered:
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:ETIMEDOUT
).connect_attempts_max_retries
attempts are made.connect_attempts_max_retries
attempts are still made, the count never goes down toconnect_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
fromHttpSM.cc
never appears.Is this a bug or am I misunderstanding how hostdb is supposed to work?
The text was updated successfully, but these errors were encountered: