https://issues.apache.org/bugzilla/show_bug.cgi?id=48735

--- Comment #8 from Adam C <[email protected]> 2011-10-31 21:10:33 UTC ---
This can be easily reproduced. The "busy" counter is not decreased when the
worker tries to send something to node which is down. For example when
receiving the "connection refused" from the server.

Have balancer for 2 members. One member should be down. Start sending messages
concurrently for some period of time (more then 60s due to "retry" timeout for
disabled worker due to errors).


Start the server which was down and continue sending messages. The started
server will not be getting messages only when the "busy" counter for the second
node will be high enough so balancers selects the first node as less busy. The
balancer thinks that the first node is still busy handling request which failed
with error due to lack of proper handling of "busy" value.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to