[jira] [Updated] (TS-608) Is HttpSessionManager::purge_keepalives() too aggressive?

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

     [ 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: 5.3.0)
                   6.0.0

> 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: Bryan Call
>             Fix For: 6.0.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.3.4#6332)