You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Mark Watts <m....@eris.qinetiq.com> on 2012/03/07 09:46:21 UTC

[users@httpd] mod_proxy_balancer error state causes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


When using mod_proxy_balancer there are several 'events' that will
place a given worker into the Err state for "retry=" seconds.

These 'events' don't all appear to be explicitly documented in once place.

Clearly any HTTP response code matching the list given in
"failonstatus=" as well as any request exceeding "timeout=" seconds
will place the worker into the Err state.

With this in mind, I have a load balancer which balances across two
IIS servers. I do not have "failonstatus=" set so I assumed that only
timeouts would cause workers to go into Err.
However, when one of the IIS boxes returns a 500, this also seems to
trigger the Err state.

Two questions:

1. Is this expected behaviour?
2. If so, do any other HTTP response codes trigger the Err state as well?

Regards,

Mark.

- -- 
Mark Watts BSc RHCE
Senior Systems Engineer, MSS Secure Managed Hosting
www.QinetiQ.com
QinetiQ - Delivering customer-focused solutions
GPG Key: http://www.linux-corner.info/mwatts.gpg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9XIF0ACgkQBn4EFUVUIO0chQCePSW3IaKMt31b+sYw8EfJDMx+
1ZkAoOzxWiMMRTCwO0lAref+m5mXqSHL
=Fknx
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] mod_proxy_balancer error state causes

Posted by Paulo Silva <pa...@gmail.com>.
Hi,

Anyone knows if this is documented somewhere?

Thanks

2012/3/7 Mark Watts <m....@eris.qinetiq.com>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> When using mod_proxy_balancer there are several 'events' that will
> place a given worker into the Err state for "retry=" seconds.
>
> These 'events' don't all appear to be explicitly documented in once place.
>
> Clearly any HTTP response code matching the list given in
> "failonstatus=" as well as any request exceeding "timeout=" seconds
> will place the worker into the Err state.
>
> With this in mind, I have a load balancer which balances across two
> IIS servers. I do not have "failonstatus=" set so I assumed that only
> timeouts would cause workers to go into Err.
> However, when one of the IIS boxes returns a 500, this also seems to
> trigger the Err state.
>
> Two questions:
>
> 1. Is this expected behaviour?
> 2. If so, do any other HTTP response codes trigger the Err state as well?
>
> Regards,
>
> Mark.
>
> - --
> Mark Watts BSc RHCE
> Senior Systems Engineer, MSS Secure Managed Hosting
> www.QinetiQ.com
> QinetiQ - Delivering customer-focused solutions
> GPG Key: http://www.linux-corner.info/mwatts.gpg
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk9XIF0ACgkQBn4EFUVUIO0chQCePSW3IaKMt31b+sYw8EfJDMx+
> 1ZkAoOzxWiMMRTCwO0lAref+m5mXqSHL
> =Fknx
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>


-- 
Paulo Silva <pa...@gmail.com>