if you REJECT from iptables you tell the client immediatly that the
service/port is not available, otherwise you run into timeouts, yes.
i'm not quite sure, but max_fails=3 x fail_timeout=30s == 90 seconds, until
your nginx fails over to the other
server.
regards,
mex
Posted at Nginx Forum:
I didn't even think about rejecting the traffic rather than dropping it!
Great idea!
Would that allow the client connection (Browser to Nginx) to fail over to
the backend server that is up rather than simply timing out?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,238894,238913#msg-2
Hello!
On Mon, May 06, 2013 at 12:12:44PM -0400, mevans336 wrote:
> Hi Mex,
>
> We shut them down one-by-one, 45 minutes apart. The issue only seems to
> occur when the first server listed is blocked however. We don't see the read
> timeouts if I leave the iptables rules enabled on the second se
Oops, here is the relevant error.log entry from Nginx as well:
013/05/06 01:46:03 [error] 2063#0: *294659 upstream timed out (110:
Connection timed out) while connecting to upstream, client: ip.address,
server: amywebsite.com, request: "GET /home HTTP/1.1", upstream:
"http://192.168.1.12:8080/home
Hi Mex,
We shut them down one-by-one, 45 minutes apart. The issue only seems to
occur when the first server listed is blocked however. We don't see the read
timeouts if I leave the iptables rules enabled on the second server. I think
that may be a false symptom related to ip_hash binding clients t
mex Wrote:
---
> ehlo,
>
>
> one question: do you shutdown all your app-servers or
> server-by-server, so you still have a available application?
my bad, please read:
do you shutdown all your app-servers at once or
server-after-server, so you
ehlo,
one question: do you shutdown all your app-servers or server-by-server, so
you still have
a available application?
there ist the "down" option for you upstream-block to disable servers, even
if they are
up, but using this in a dynamic process might get very frickling.
whet do you use f
Hello,
Each night we take our backend servers offline at specific times for
maintenance. When the application servers restart they immediately begin
answering HTTP requests from Nginx, but we want to keep them out of the
upstream pool for about 30 minutes while they cache information from our
data
