Re: Connection statuses

On Thursday 19 February 2015 15:46:46 K Young wrote: > In nginx Open, it looks like when a connection can't be assigned to a > request, it is dropped and not enqueued for later processing. Is this > correct? I don't understand what you mean by "a connection can't be assigned to a request". > If s

Re: Connection statuses

In nginx Open, it looks like when a connection can't be assigned to a request, it is dropped and not enqueued for later processing. Is this correct? If so is the number of dropped connections equal to the difference between active and handled? On Thu, Feb 19, 2015 at 10:34 AM, Valentin V. Bartenev

Re: Connection statuses

On Thursday 19 February 2015 10:12:02 K Young wrote: > Thanks Maxim, that's what I needed to know. > > How common would you say it is to use accept filters / deferred accept on > nginx in production? > > Also to be perfectly certain: connections.idle >

Re: Connection statuses

Thanks Maxim, that's what I needed to know. How common would you say it is to use accept filters / deferred accept on nginx in production? Also to be perfectly certain: connections.idle in Plus is the same as Waiting

Re: Connection statuses

Hello! On Wed, Feb 18, 2015 at 09:25:01PM -0500, K Young wrote: > Hello, I've been reading through nginx source to understand the metrics > that are > reported. I've got an idea of what is happening, but since the flow is > asynchro