You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Thomas Jackson (JIRA)" <ji...@apache.org> on 2016/08/18 16:59:21 UTC
[jira] [Commented] (TS-4346) Requests that hit conneciton limits
(max_origin_connections, etc.) incur a hard coded latency hit
[ https://issues.apache.org/jira/browse/TS-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426809#comment-15426809 ]
Thomas Jackson commented on TS-4346:
------------------------------------
Why would we close this won't fix? We simply need to queue the connections
when they hit the limit instead of sleeping.
> Requests that hit conneciton limits (max_origin_connections, etc.) incur a hard coded latency hit
> -------------------------------------------------------------------------------------------------
>
> Key: TS-4346
> URL: https://issues.apache.org/jira/browse/TS-4346
> Project: Traffic Server
> Issue Type: Bug
> Components: Network
> Reporter: Thomas Jackson
>
> example: https://github.com/apache/trafficserver/blob/master/proxy/http/HttpSM.cc#L4741
> Ideally this would instead put the transaction in some queue to be processed, such that the transaction could be resumed as soon as a connection becomes available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)