[GitHub] [trafficserver] shinrich commented on issue #7290: Clarification and/or configurability of what it means for a server to be dead/down

[GitBox <gi...@apache.org>]

shinrich commented on issue #7290:
URL: https://github.com/apache/trafficserver/issues/7290#issuecomment-815922190


   I ran across the proxy.config.http.down_server.abort_threshold setting.  I think the comparison is backwards from the description.  But if the client times out in more than this many seconds and the origin hasn't sent anything back yet, it will count towards marking that origin down.   The default value for this setting is 10..
   
   The intent is to include "slow servers" in the set of dead servers to be avoided.  But if your client side inactivity timeout is less than your origin side inactivity, the bad client scenario that @djcarlin identifies will trigger this and increment the counts for the origin connection to be down.
   
   It is easy enough to take proxy.config.http.down_server.abort_threshold out of the equation by setting it higher than any of your inactivity timeouts.  But I think we may want to reconsider this setting.  The intent of marking "slow" servers as down is admirable, but identifying the slowness as an issue on the origin side vs the client side is sketchy at best.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org