Yes, the first thing that helped us with connection issues was setting
the origin_max_connections to a reasonable value, either per cache or
per remap depending on traffic but we would always have a cache upper
limit. However in a 2-tier setup if you only do this at one tier you
back up the connect
Thank Evan. In our case, the edge’s
origin_max_connections: 0
net.connection_throttle:50
parent_proxy.total_connect_attemps:6
parent_proxy.per_parent_connec_attempts:1
Do you think we are subject to the looping condition this commit addresses?
-Hongfei
> On Sep 30, 2020, at 2:37 PM, Evan Z
This sounds similar to issues we have had in the past. I think this
was fixed in 7x with this commit,
https://github.com/apache/trafficserver/commit/1da4fbcd5fd32ff86888ed401e0c297b22e00c52
. There have been a few other commits past that for other tight loop
scenarios when dealing with the connecti
Hi Folks,
In a 2-tier CDN production environment using ATS, we recently had a series of
issues that I want to reach out to the community for help.
The symptoms usually shows up on edge caches as:
1) elevated CPU - noticeable, but not 'through the roof'
2) unusually high ingress
