You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2013/05/03 22:30:16 UTC
[jira] [Updated] (TS-1578) connection management
[ https://issues.apache.org/jira/browse/TS-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Peach updated TS-1578:
----------------------------
Summary: connection management (was: connection manage)
> connection management
> ---------------------
>
> Key: TS-1578
> URL: https://issues.apache.org/jira/browse/TS-1578
> Project: Traffic Server
> Issue Type: Improvement
> Components: Network
> Affects Versions: 3.2.0
> Reporter: Bin Chen
> Assignee: Bin Chen
> Fix For: 3.3.5
>
>
> ts must handle some connection cases:
> 1、receiving large concurrent connections suddenly
> 2、have slow original server(incomming producer greater than consumer), so will be throttling. if throttling, ts will restart. Replacing throttling to max_accept limmiting maybe more friendly?
> 3、different domain have different origin_max_connections?
> 4、how to handle health check if use max_accept?
--
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