You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "Wendy Huang (JIRA)" <ji...@apache.org> on 2010/02/12 03:06:27 UTC
[jira] Created: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
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
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.
[jira] Commented: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Wendy Huang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832790#action_12832790 ]
Wendy Huang commented on TS-176:
--------------------------------
Need to merge the change to ATS
> 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
>
> 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.
[jira] Issue Comment Edited: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833138#action_12833138 ]
Leif Hedstrom edited comment on TS-176 at 2/12/10 8:11 PM:
-----------------------------------------------------------
Also update
http://cwiki.apache.org/confluence/display/TS/2_0-Features
I updated the CWiki pages, so there is now only one page with "features" for 2.0.
was (Author: zwoop):
Also update
http://cwiki.apache.org/confluence/display/TS/Release-2.0
(unless we've eliminated this for some other page).
> 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.
[jira] Issue Comment Edited: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Bryan Call (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Bryan Call (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833112#action_12833112 ]
Bryan Call commented on TS-176:
-------------------------------
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.
[jira] Assigned: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Bryan Call (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Call reassigned TS-176:
-----------------------------
Assignee: Bryan Call
> 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
> Assignee: Bryan Call
> 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.
[jira] Commented: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833155#action_12833155 ]
Leif Hedstrom commented on TS-176:
----------------------------------
Also, I would suggest, once we fix the stats bug(s), so that the connection counter is accurate, I think we should deprecate this option. I mean, if the counters are right, there ought to be no need to have this option (because you'll fail anyways if you hit the throttle, with an out of FD error).
> 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.
[jira] Updated: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Wendy Huang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Huang updated TS-176:
---------------------------
Attachment: TS-176.patch
patch file attached.
> 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
> 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.
[jira] Commented: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833138#action_12833138 ]
Leif Hedstrom commented on TS-176:
----------------------------------
Also update
http://cwiki.apache.org/confluence/display/TS/Release-2.0
(unless we've eliminated this for some other page).
> 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.
[jira] Resolved: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Bryan Call (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Call resolved TS-176.
---------------------------
Resolution: Fixed
> 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
> Assignee: Bryan Call
> 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.
[jira] Updated: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Bryan Call (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Call updated TS-176:
--------------------------
Fix Version/s: 2.0.0a
> 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.
[jira] Commented: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Miles Libbey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833114#action_12833114 ]
Miles Libbey commented on TS-176:
---------------------------------
Sounds like this will need a documentation update too?
If so, please suggest where it should appear in docs, and some content -- perhaps assign to Diane S when done?
> 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.
[jira] Commented: (TS-176) added a variable
proxy.config.net.throttle_enabled, which is enabled by default
Posted by "Bryan Call (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833109#action_12833109 ]
Bryan Call commented on TS-176:
-------------------------------
reviewed: looks good
> 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.