[
https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833112#action_12833112
]
Bryan Call edited comment on TS-176 at 2/12/10 6:51 PM:
--------------------------------------------------------
There is an issue around the global counter being off when using the accept
thread. We use RecIncrGlobalRawStatSum() when we accept the connection in
NetAccept::do_blocking_accept(). And decrement the count later when the
connection is closed.
I think it is still valid to have this feature/workaround in until we are
comfortable that the connection counts are correct. We might want to remove it
later, but that is debatable.
was (Author: bcall):
The number of connections was incorrect because of the stats being off.
However, TS-162 should resolve the issue of the connection counts being
incorrect.
I think it is still valid to have this feature/workaround in until we are
comfortable that the connection counts are correct. We might want to remove it
later, but that is debatable.
> added a variable proxy.config.net.throttle_enabled, which is enabled by
> default
> -------------------------------------------------------------------------------
>
> Key: TS-176
> URL: https://issues.apache.org/jira/browse/TS-176
> Project: Traffic Server
> Issue Type: Improvement
> Reporter: Wendy Huang
> Priority: Minor
> Fix For: 2.0.0a
>
> Attachments: TS-176.patch
>
>
> This is copied from bugzilla 3034748.
> original description:
> our YTS hosts started throttling connections, causing a site-wide outage.
> The throttle was engaged because the
> proxy.process.http.current_server_connections exceeded the configured 10000
> threshold. Actual connections as measured in netstat were much lower.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.