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

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

    [ https://issues.apache.org/jira/browse/TS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976179#action_12976179 ] 

mohan_zl commented on TS-608:
-----------------------------

Now we are writing a l7 health check module, and i agree with your idea. Maybe we can do it when finish current work, if it is not very urgent.

> 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: 2.1.6
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.