[
https://issues.apache.org/jira/browse/TS-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622703#comment-13622703
]
David Carlin commented on TS-1801:
----------------------------------
I've been setting proxy.config.net.throttle_enabled = 0 because I've
experienced a number of times where a throttling event occurs and you can no
longer reach ATS. Only way to recover is by restarting it.
I'm not sure if my past experience is related to TS-1672 - this seems to
pertain to 'emergency throttling'. I set throttle_enabled = 0 because I would
get a series of "too many connections, throttling" messages in traffic.out that
were unrecoverable.
The situation where fds_limit is hit seems to result in "WARNING: too many open
file descriptors, emergency throttling" which is what TS-1672 seems to be
referring to. Its unclear if this fixes the issue that caused me to use
throttle_enabled.
Can you also clarify if this statement in the FAQ is correct:
http://trafficserver.apache.org/docs/trunk/admin/faqs/
A connection throttle event occurs when client or origin server connections
reach 90% of half the configured limit (3600 by default).
> Remove proxy.config.net.throttle_enabled
> ----------------------------------------
>
> Key: TS-1801
> URL: https://issues.apache.org/jira/browse/TS-1801
> Project: Traffic Server
> Issue Type: Improvement
> Components: Network
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Fix For: 3.3.2
>
>
> This setting is fairly nonsensical, and, it seems it was added a while ago
> when we had issues with leaking FDs and/or stats:
> {code}
> TS_INLINE int
> check_net_throttle(ThrottleType t, ink_hrtime now)
> {
> if(throttle_enabled == false) {
> // added by Vijay to disable throttle. This is done find out if
> // there any other problem other than the stats problem -- bug 3040824
> return false;
> }
> {code}
> This setting just makes no sense, because we really honor
> proxy.config.net.connections_throttle, which also controls the amount of FDs
> we setrlimit() on.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
