Here's the relevant discussion:
https://groups.google.com/forum/?fromgroups=#!topic/linux_net/ACDB15QbHls
And thanks for making nginx awesome! :)
On Tue, Mar 19, 2013 at 3:42 PM, Jay Oster wrote:
> Hi Andrei!
>
> On Tue, Mar 19, 2013 at 2:49 AM, Andrei Belov wrote:
>
>> Hel
Hi Andrei!
On Tue, Mar 19, 2013 at 2:49 AM, Andrei Belov wrote:
> Hello Jay,
>
> If I understand you right, issue can be repeated in the following cases:
>
> 1) client and server are on different EC2 instances, public IPs are used;
> 2) client and server are on different EC2 instances, private I
Hi Maxim,
On Tue, Mar 19, 2013 at 7:19 AM, Maxim Dounin wrote:
> Hello!
>
> As far as I understand, tcp_max_syn_backlog configures global
> cumulative limit for all listening sockets, while somaxconn limits
> one listening socket backlog. If any of the two is too small -
> you'll see SYN packet
Hi Maxim,
On Sun, Mar 17, 2013 at 4:42 AM, Maxim Dounin wrote:
> Hello!
>
> On "these hosts"? Note that listen queue aka backlog size is
> configured in _applications_ which call listen(). At a host level
> you may only configure somaxconn, which is maximum allowed listen
> queue size (but an
ppening on a single machine; the TCP stack is
involved, but not a physical network. The only common denominator is nginx.
On Fri, Mar 15, 2013 at 1:20 AM, Maxim Dounin wrote:
> Hello!
>
> On Thu, Mar 14, 2013 at 07:07:20PM -0700, Jay Oster wrote:
>
> [...]
>
> > The acce
Hi list!
I'm trying to debug an interesting problem where we randomly get a "high
latency" response time from our upstream servers. It appears to occur in
about 1.5% of all requests. Here's a description of the tests I've been
running to isolate the problem within nginx:
I'm using an endpoint on
