Hello!
On Mon, Feb 23, 2015 at 07:27:25AM -0500, Gona wrote:
> Hi Maxim,
>
> If possible I would like to use a keep-alive connection timeout less than
> that of the backend servers to avoid premature connection close by backend
> server. As mentioned before, I am trying to avoid other options l
Hi Maxim,
If possible I would like to use a keep-alive connection timeout less than
that of the backend servers to avoid premature connection close by backend
server. As mentioned before, I am trying to avoid other options like
rerouting using proxy_next_upstream or retrying by downstream client.
Hello!
On Thu, Jan 15, 2015 at 10:53:40AM -0500, Gona wrote:
> So my understanding from this is - the race condition is possible and when
> it happens with one server in the upstream block or "proxy_next_upstream"
> set to OFF, Nginx will return back an error without retrying. Is this
> right?
Y
Hi Maxim,
Thanks for the response.
So my understanding from this is - the race condition is possible and when
it happens with one server in the upstream block or "proxy_next_upstream"
set to OFF, Nginx will return back an error without retrying. Is this
right?
Thanks,
Gopala
Posted at Nginx For
Hello!
On Tue, Jan 06, 2015 at 06:06:18AM -0500, Gona wrote:
> I have Nginx server configured with couple of backend servers with keepalive
> connections enabled.
>
> I am trying to understand what will be the Nginx's behaviour in case the
> connection is closed by an upstream server legitimatel
I have Nginx server configured with couple of backend servers with keepalive
connections enabled.
I am trying to understand what will be the Nginx's behaviour in case the
connection is closed by an upstream server legitimately when Nginx is trying
to send a new request exactly at the same time. In
