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

Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2014/05/19 20:52:40 UTC

[jira] [Updated] (TS-2523) automatically max out the listen backlog

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

Bryan Call updated TS-2523:
---------------------------

    Fix Version/s:     (was: 5.0.0)
                   sometime

> automatically max out the listen backlog
> ----------------------------------------
>
>                 Key: TS-2523
>                 URL: https://issues.apache.org/jira/browse/TS-2523
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core, Network
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: sometime
>
>
> Rather than choosing the right value for {{proxy.config.net.listen_backlog}}, we should support a -1 default. This would max out the listen backlog on systems where we know how to find that, and set it to {{SOMAXCON}} everywhere else.
> On Linux, the max backlog is 65535 (unsigned short), and the kernel will clip that to {{/proc/sys/net/core/somaxconn}}.



--
This message was sent by Atlassian JIRA
(v6.2#6252)