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

2015-06-11 Thread Phil Sorber (JIRA)

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

Phil Sorber updated TS-608:
---
Fix Version/s: (was: 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
 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)


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

2015-03-09 Thread Leif Hedstrom (JIRA)

 [ 
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)


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

2014-11-20 Thread Leif Hedstrom (JIRA)

 [ 
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.2.0)
   5.3.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: 5.3.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)


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

2014-11-04 Thread Susan Hinrichs (JIRA)

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

Susan Hinrichs updated TS-608:
--
Assignee: (was: Bin Chen)

 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: 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.3.4#6332)


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

2014-11-04 Thread Susan Hinrichs (JIRA)

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

Susan Hinrichs updated TS-608:
--
Assignee: Bryan Call

 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: 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.3.4#6332)


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

2013-04-12 Thread weijin (JIRA)

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

weijin updated TS-608:
--

Assignee: Bin Chen

 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: 3.3.3

 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


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

2013-04-10 Thread Leif Hedstrom (JIRA)

 [ 
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.2)
   3.3.3

 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.3

 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


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

2013-03-19 Thread Leif Hedstrom (JIRA)

 [ 
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


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

2011-10-04 Thread Leif Hedstrom (Updated) (JIRA)

 [ 
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.1.1)
   3.3.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
 Fix For: 3.3.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




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

2011-01-17 Thread mohan_zl (JIRA)

 [ 
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.