Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 972949

Summary:	'mod_proxy_balancer' algorithm 'bybusyness' does not balance the load after failed worker has recovered
Product:	Red Hat Enterprise Linux 6	Reporter:	Josep 'Pep' Turro Mauri <pep>
Component:	httpd	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED ERRATA	QA Contact:	Filip Holec <fholec>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.4	CC:	jkaluza, jorton, mbabacek, mschuppe, psplicha, thomas.oulevey
Target Milestone:	rc	Keywords:	Patch
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-14 08:07:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	994246, 1056252

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