You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2016/08/23 19:29:22 UTC

[jira] [Updated] (TS-4342) Connections queued when hitting `proxy.config.http.origin_max_connections` don't honor order

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

Leif Hedstrom updated TS-4342:
------------------------------
    Fix Version/s: sometime

> Connections queued when hitting `proxy.config.http.origin_max_connections` don't honor order
> --------------------------------------------------------------------------------------------
>
>                 Key: TS-4342
>                 URL: https://issues.apache.org/jira/browse/TS-4342
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Network
>            Reporter: Thomas Jackson
>            Assignee: Thomas Jackson
>             Fix For: sometime
>
>
> As of today when you hit `proxy.config.http.origin_max_connections` requests are queued waiting for an available connection to origin. Today this is done by simply [rescheduling 100ms in the future|https://github.com/apache/trafficserver/blob/master/proxy/http/HttpSM.cc#L4756]. Ideally this would honor the order with which the requests came in.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)