Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow increasing SOMAXCONN on listeners #8986

Closed
appliedprivacy opened this issue Mar 30, 2020 · 0 comments · Fixed by #8994
Closed

allow increasing SOMAXCONN on listeners #8986

appliedprivacy opened this issue Mar 30, 2020 · 0 comments · Fixed by #8994

Comments

@appliedprivacy
Copy link
Contributor

  • Program: dnsdist
  • Issue type: Feature request

Short description

from: https://mailman.powerdns.com/pipermail/dnsdist/2020-March/000809.html

Hi Christoph,

On 3/29/20 8:25 PM, Christoph via dnsdist wrote:

after restarting dnsdist we noticed that while nginx takes
the new setting into account dnsdist remains at 128:

netstat -Lan
Current listen queue sizes (qlen/incqlen/maxqlen)
Proto Listen
tcp4 0/0/128 <<< dnsdist
tcp4 5/0/2048 <<< nginx

Is there a way to tell dnsdist to increase the connection queue on the
DoH listener?

I'm afraid there is currently no way to do this. We call listen() with
SOMAXCONN, which defaults to 128 on most Unixes. We could make that
value configurable since SOMAXCONN is no longer an hard limit on several
systems including Linux, so please open a feature request 1 if you
think it's worth it.

I also tried:
setMaxTCPQueuedConnections(2048)

from:
https://dnsdist.org/reference/tuning.html

This is an unrelated setting, controlling the number of connections we
are willing to queue in our internal pipe.

Best regards,
Remi Gacogne

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants