[
https://issues.apache.org/jira/browse/TS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-608:
------------------------
Attachment: TS-608.patch
change the logic:
1 if we trigger "max server connections", remove one keep-alive connections
from every dlist of every session bucket in HttpSessionManager
2 if we trigger per-origin limits, just remove all connections related with
that origin server
> 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.1
>
> 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.
-
You can reply to this email to add a comment to the issue online.
