Questions regarding worker_connections
aldernetwork at gmail.com
Mon Aug 27 17:31:13 UTC 2018
Thanks Maxim for the info. So worker connections in waiting state may not
ready to be reused. Is there any maximum waiting time? We seem to run into
a condition that those connections are permanently stuck in waiting state.
Also, what would be the ball-park number of worker_connections should be
if we want to support expected number of active connections, say 150?
On Mon, Aug 27, 2018 at 4:56 AM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> On Fri, Aug 24, 2018 at 02:54:31PM -0700, Alder Netw wrote:
> > Got a question regarding the worker_connections configuration. Is a
> > worker_connection
> > essentially
> > a tcp socket connection or http session?
> The worker_connections directive configures maximum number of
> connections a worker process can open. That is, basically this
> means "TCP sockets".
> See http://nginx.org/r/worker_connections for additional details.
> > Via the http_stub_status_module, I can see there are
> > connections in waiting state, but any new request
> > will result in a "worker connections are not enough"
> > alert in error.log. Why it cannot accept new connections
> > if there are existing connections in waiting state? Is that
> > a bug? I am using nginx 1.6.2.
> Connections in the waiting state are real established connections.
> While in some cases nginx can close and re-use these connections
> quickly enough to don't trigger the "worker connections are not
> enough" alert, this is not something guaranteed.
> In general, you should tune worker_connections so it's higher than
> expected number of active connections - that is, all connections
> including waiting ones.
> Maxim Dounin
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx