[
https://issues.apache.org/jira/browse/TS-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007427#comment-15007427
]
ASF subversion and git services commented on TS-2523:
-----------------------------------------------------
Commit b2c697be5f351ee1bdd77c76165ed2d71a24343e in trafficserver's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=b2c697b ]
TS-2523: automatically max out the listen backlog
Automatically detect and set the listen backlog to the system
maximum, falling back to the previous default for compatibility.
> 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
> Labels: incompatible, yahoo
> 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.3.4#6332)
