Port Exhaustion - SQL
brandonm at medent.com
Thu May 16 13:11:39 UTC 2019
Yes all of those changes you have mentioned have been made.
Network & Systems Engineer
15 Hulbert Street
Auburn, NY 13021
Phone: [ callto:(315)-255-0900 | (315)-255-0900 ]
Fax: [ callto:(315)-255-3539 | (315)-255-3539 ]
Web: [ http://www.medent.com/ | www.medent.com ]
This message and any attachments may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by e-mail, and permanently delete this e-mail.
From: "Reinis Rozitis" <r at roze.lv>
To: "nginx" <nginx at nginx.org>
Sent: Thursday, May 16, 2019 9:09:25 AM
Subject: RE: Port Exhaustion - SQL
> We have made all the changed we could in the kernel to help with this but still hitting limits.
What changes have you made?
Usually the port limit is reached because of time wait sockets.
If not done already try with:
net.ipv4.ip_local_port_range = 1028 65535
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_fin_timeout = 30
Increasing the ephemeral port range (usually by default it starts around 30k so you effectively lose 30k ports - obviously adjust the lower limit to your application needs).
Then time wait socket reuse helps a lot and also decreasing the FIN timeout (the default is something like 60 seconds).
nginx mailing list
nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx