Mladen Turk wrote: > > Jim Jagielski wrote: > > > >> > >> The only problem is that it's not documented ;) > >> > > > > Hmm... I thought that this happened via the code > > in find_session_route() and relied on sticky sessions; > > but again iirc they can be via cookies as well. > > So one issue is that stickysession must be used, I think. > > > > Right. Also if the sessions are not replicated it makes no > sense to have hot-standby, cause the user will have to > login again. > > find_session_route will check for 'redirect' if all other nodes > are unusable (in error or stopped) and make a failover.
Yes, assuming a sticky session has been setup. For HTTP, though, having hot-standby even without sessions makes a lot of sense in a lot of cases (think of something like images.foo.com which handles static images). The rub there is, I think, that this relies on forcing HTTP cookies on all HTTP servers in the balancer, instead of having the logic itself contained "totally" (as much as possible) in the balancer code (eg, afaik, we look for the cookie but we don't set it anyplace). That's what I meant by looking into this post 2.2.1; having a sort of 'standby' condition, in addition to enabled and disabled. -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "If you can dodge a wrench, you can dodge a ball."
