Cause: When using mod_proxy_balancer with lbmethod_bybusyness, the "busy" counter was not decreased when the worker tried to send a request to non-working node.
Consequence: Once the non-working node became working again, mod_proxy_balancer did not recover the worker, because the "busy" counter still signalled the worker is busy.
Fix: The "busy" counter is decreased after failed requests.
Result: mod_proxy_balancer uses the worker after the node recovery.
Description of problem:
Apache 'mod_proxy_balancer' algorithm 'bybusyness' does not balance the load after failed worker has recovered. This issue does not occur with the default method (byrequests).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
see bug 601132 or upstream bug report
This was reported in EWS in bug 899273
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.