[ 
https://issues.apache.org/jira/browse/TS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-608:
-----------------------------

    Fix Version/s:     (was: 3.3.3)
                   3.3.2
    
> 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.2
>
>         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

Reply via email to