blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px
#715FFA solid !important; padding-left:1ex !important; background-color:white
!important; } Hmm...I'm not sure to agree that the majority of the congestion
control feature is covered by origin_max_connections. Congestion control
feature as defined has a "mechanism" to mark an origin congested, which afaik
origin_max_connections doesn't support.
Do you actually see a more compelling reason to deprecate the feature other
than not finding any active users? Fwiw, I've experimented this feature a bit
(and it seems to work the way I expected it to work) have plans on using it in
the near future. So, unless there are strong reasons that indicate this feature
not working well in conjunction with other features and is not easy to fix
without breaking a lot of things around, I'd prefer to continue to keep the
feature.
Thanks,
Sudheer
On Monday, May 9, 2016, 5:59 PM, Sudheer Vinukonda <[email protected]>
wrote:
Hmm..I'm not sure to agree that majority of this functionality
On Monday, May 9, 2016, 5:55 PM, Thomas Jackson <[email protected]> wrote:
I'd like to propose we deprecate and remove the "congestion control" features
within ATS. Currently this feature is disabled by default, and from my
interactions I can't seem to find anyone that uses this feature. In addition,
the majority of this functionality is covered with `origin_max_connections`.
Appreciate any feedback.
Congestion control references:
- Docs:
https://docs.trafficserver.apache.org/en/5.3.x/admin/http-proxy-caching.en.html#using-congestion-control
- Config:
https://docs.trafficserver.apache.org/en/5.3.x/reference/configuration/congestion.config.en.html
