Bug 972949 - 'mod_proxy_balancer' algorithm 'bybusyness' does not balance the load after failed worker has recovered
Summary: 'mod_proxy_balancer' algorithm 'bybusyness' does not balance the load after f...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: httpd
Version: 6.4
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Web Stack Team
QA Contact: Filip Holec
URL:
Whiteboard:
Depends On:
Blocks: 994246 1056252
TreeView+ depends on / blocked
 
Reported: 2013-06-10 21:26 UTC by Josep 'Pep' Turro Mauri
Modified: 2018-12-09 17:02 UTC (History)
7 users (show)

Fixed In Version: httpd-2.2.15-31.el6
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2014-10-14 08:07:29 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Priority Status Summary Last Updated
Apache Bugzilla 48735 None None None Never
Red Hat Product Errata RHBA-2014:1386 normal SHIPPED_LIVE httpd bug fix and enhancement update 2014-10-14 01:27:20 UTC

Description Josep 'Pep' Turro Mauri 2013-06-10 21:26:03 UTC 
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):
httpd-2.2.15-28.el6_4

How reproducible:
Always

Steps to Reproduce:
see bug 601132 or upstream bug report

Additional info:
This was reported in EWS in bug 899273
Comment 11 errata-xmlrpc 2014-10-14 08:07:29 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2014-1386.html
Note You need to log in before you can comment on or make changes to this bug.