On Apr 17, 2008, at 8:56 AM, Plüm, Rüdiger, VF-Group wrote:
-----Ursprüngliche Nachricht-----
Von: William A. Rowe, Jr.
Gesendet: Donnerstag, 17. April 2008 14:49
An: [email protected]
Betreff: low hanging fruit in proxy_balancer
One of our class attendees this week had an interesting suggesting
for
a balancer-manager feature. Right now each member is a
2-state, either
enabled or disabled.
For session stickiness, he suggested a tristate third option to bleed
out the remaining sessions, dispatching no /new/ sessions into the
particular member. This would let the existing sessions drain and
complete, in order to take down a member without disrupting
any logins.
In principle we already have this, but we do not make any difference
between
PROXY_WORKER_DISABLED and PROXY_WORKER_STOPPED and of course we are
are missing
the needed field in the balancer manager of course to switch between
enabled,
disabled and stopped.
Yeah, but we *should* differentiate between the 2. There are (well,
should be) administrative status and "runtime" status.
