You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/03/19 18:13:15 UTC
[jira] [Commented] (TS-608) Is
HttpSessionManager::purge_keepalives() too aggressive?
[ https://issues.apache.org/jira/browse/TS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606526#comment-13606526 ]
Leif Hedstrom commented on TS-608:
----------------------------------
Wow, this is an old patch. Mohan or anyone in Taobao, is this patch still relevant? If so, can you rebase it for current master, and post again?
> Is HttpSessionManager::purge_keepalives() too aggressive?
> ----------------------------------------------------------
>
> Key: TS-608
> URL: https://issues.apache.org/jira/browse/TS-608
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Leif Hedstrom
> Fix For: 3.3.3
>
> Attachments: TS-608.patch
>
>
> It seems that if we trigger the "max server connections", we call this purge function in the session manager, which will close all currently open keep-alive connections. This seems very aggressive, why not limit it to say only removing 10% of each "bucket" or some such? Also, how does this work together with per-origin limits? Ideally, if the per-origin limits are in place, we would only purge sessions that are for the IP we wish to connect to ?
--
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