Question on Nginx threads writing

fotografik

Active member
A question for the Nginx experts in here. Is it normal for the Nginx threads that are actively writing to steadily increase? Please see our Munin graphs attached.

nginx_munin_cs.webp
 
Can be normal but can also be nginx bug https://serverfault.com/questions/6...nx-to-accumulate-connections-in-writing-state. Writing = connections writing to client/visitors. So gradual increase in concurrent visitors over time where nginx isn't restarted maybe.

http://nginx.org/en/docs/http/ngx_http_stub_status_module.html#stub_status

Active connections
The current number of active client connections including Waiting connections.

accepts
The total number of accepted client connections.

handled
The total number of handled connections. Generally, the parameter value is the same as accepts unless some resource limits have been reached (for example, the worker_connections limit).

requests
The total number of client requests.

Reading
The current number of connections where nginx is reading the request header.

Writing
The current number of connections where nginx is writing the response back to the client.

Waiting
The current number of idle client connections waiting for a request.

Bug wise, specifically
There is at least one connection leak in HTTP/2 as fixed in nginx 1.11.3, and the fix is not yet available in 1.10.x. Please try 1.11.x instead.
What version of Nginx you using ? I don't see such and use Centmin Mod LEMP with nginx 1.13.12 right now.
 
Ah that could explain it. We are on 1.10.3 on Ubuntu 16.04LTS at the moment and I will update it to 1.11.x now. Thank you.

p.s. glad to bump into you here. We have had some interactions before on the vBulletin forums, and your guides on how to update vBulletin and general tuning have helped me a lot.
 
Just to close off this thread. Updating Nginx to 1.11.3 solved the issue for me. Nginx memory usage also dropped by half so bonus!

13_nginx_munin_1.webp
13_nginx_munin_2.webp
 
p.s. glad to bump into you here. We have had some interactions before on the vBulletin forums, and your guides on how to update vBulletin and general tuning have helped me a lot.
Glad I could help :)

Just to close off this thread. Updating Nginx to 1.11.3 solved the issue for me. Nginx memory usage also dropped by half so bonus!

Great to hear though Nginx 1.11 is still ancient as Nginx latest stable is 1.14.0 (same as 1.13.12 mainline) right now http://nginx.org/en/download.html
 
Top Bottom