You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Brian Geffon (JIRA)" <ji...@apache.org> on 2014/06/02 20:40:02 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=14015714#comment-14015714 ] 

Brian Geffon commented on TS-608:
---------------------------------

We can only purge up to 75% of the limit or something?

> 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
>            Assignee: Bin Chen
>             Fix For: 5.2.0
>
>         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 was sent by Atlassian JIRA
(v6.2#6252)