[jira] [Commented] (TS-2523) automatically max out the listen backlog
[ https://issues.apache.org/jira/browse/TS-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008078#comment-15008078 ] seri,Kim commented on TS-2523: -- Hi, I think that we have to use /proc/sys/net/core/somaxconn instead of /proc/sys/net/ipv4/tcp_max_syn_backlog. What do you think? > 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: 6.1.0 > > > 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)
[jira] [Commented] (TS-2523) automatically max out the listen backlog
[ https://issues.apache.org/jira/browse/TS-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007474#comment-15007474 ] ASF subversion and git services commented on TS-2523: - Commit b89553001ad258f2dfe31b5e3e9df87a98219f0d in trafficserver's branch refs/heads/master from [~jpe...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=b895530 ] TS-2523: fixed unused variable warning > 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: 6.1.0 > > > 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)
[jira] [Commented] (TS-2523) automatically max out the listen backlog
[ 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 [~jpe...@apache.org] [ 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)
[jira] [Commented] (TS-2523) automatically max out the listen backlog
[ https://issues.apache.org/jira/browse/TS-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966153#comment-14966153 ] zxcvbn4038 commented on TS-2523: BTW, I believe that listen(fd, -1) is only supported on Linux 2.6.39 and above, and glib support is also required. There should probably be a sane default for earlier versions, or the somaxocnn value should be queried. > 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)
[jira] [Commented] (TS-2523) automatically max out the listen backlog
[ https://issues.apache.org/jira/browse/TS-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957147#comment-14957147 ] zxcvbn4038 commented on TS-2523: [~jamespeach][~dcarlin] This option is also undocumented, as part of this change documentation should be added. > 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 > 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)
[jira] [Commented] (TS-2523) automatically max out the listen backlog
[ https://issues.apache.org/jira/browse/TS-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956229#comment-14956229 ] David Carlin commented on TS-2523: -- A new ATS user ran into this issue during load testing while evaluating ATS; it would be nice if -1 existed and was the default > 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 > 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)