[GitHub] jhg03a opened a new issue #3006: DS health protocol loophole

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

jhg03a opened a new issue #3006: DS health protocol loophole
URL: https://github.com/apache/trafficcontrol/issues/3006
 
 
   Today in ATS you may configure origin throttle limits both at a global server level and per ds. The global limits are part of astats, and therefore can be set to a threshold value that should be the same or near the actual global limit parameter. The per DS throttle limits are not part of astats I think, and even if they were, traffic monitor evaluates health at a server level not a ds level. Presently if you use per ds throttle limits and those limits are reached there is no feedback loop to TR informing it to no longer consider that overloaded cache as healthy. Currently humans have to be watching ATS log files to know when to either adjust dispersion or raise the throttle limit. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services