On Thu, 07 Mar 2019 13:33:39 -0500
"wkbrad" wrote:
> Hi all,
>
> I just wanted to share the details of what I've found about this
> issue. Also thanks to Maxim Dounin and Reinis Rozitis who gave some
> really great answers!
>
> The more I look into this the more I'm convinced this is an issue
>
Its simple..Nginx has a master process and number of worker process as you
configure in nginx.conf . Its the workers that handle connections and each
one does async
When you do a HUP, all the master process is doing is spawning n new
workers and all new connections to port 80/443 are handled by th
Thanks, Anoop! But I don't think you understood the point I was trying to
get across. I was definitely not trying to compare nginx and apache memory
usage. Let's just ignore that part was ever said. :)
I'm trying to understand why Nginx is using 2x the memory usage when the HUP
signal is sent,
Nginx does use more ram for the number of vhosts than Apache does
http://nginx.org/en/docs/control.html
The USR2 is for binary in-place upgrades and normally you should just send
a SIGHUP, I have seen sometimes the USR2 leading multiple master process
and showing some weird behaviour
You can pro
On Wed, Mar 06, 2019 at 03:49:15PM -0500, Brandon Mallory wrote:
Hi there,
> Good Advice, After doing some further research. Can you give me your opinion
> in regards to using the ssl_preread_server_name. So as long as I can get a
> SNI and then filter TCP connection to the proper server with t
Hi all,
I just wanted to share the details of what I've found about this issue.
Also thanks to Maxim Dounin and Reinis Rozitis who gave some really great
answers!
The more I look into this the more I'm convinced this is an issue with Nginx
itself. I've tested this with 3 different builds now an
Hi
I have this buggy backend application where I try to let Nginx sort out the
problems.
Example of required redirect:
http://ex.org/foo -> https://ex2.org/foo/# Nx solves the bug here
http://ex.org/foo/ -> https://ex2.org/foo/
http://ex.org/foo/?id=7 -> https://ex2.org/?id=7
Here is my curr
Thanks! Indeed, `http2_max_requests` does close the tcp connection;
BTW, I've confirmed that it is a bug of grpc-go. Thanks again!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,283297,283304#msg-283304
___
nginx mailing list
nginx@nginx.org
