Hi Malcolm, sorry I did not notice your first report.
First, Cyril is right. Weight 0 will never affect persistence and it is fortunate because weight only applies to LB while persistence is a way to bypass LB. On Tue, Mar 01, 2011 at 04:17:30PM +0000, Malcolm Turnbull wrote: > Cyril et al. > Just to confirm after further testing this is definitely to do with > keep-alive from browsers not closing the current connection to a > keep-alive server. Yes indeed. As long as the connection remains active between both ends, the serverdoes not have to be re-selected so at no point is there any behaviour change. > So if you set a server to maintenance mode connections will > effectively be drained (which is normally a good thing). > It would be nice to have the option of killing the connections > instantly as well though i.e. drain or kill (especially for things > like RDP/Exchange etc.) Good point. I know I will have to handle that for HTTP keep-alive on the server, but that will be different, we'll simply force connections to close upon the last response if the server is disabled. What you're describing is much more complicated and would require that we had a "kill now" flag in every session, that would preempt any other processing. It should be feasible on a session basis (eg: kill one session from the command line) but it will be a tougher work to be able to enumerate them by server (right now sessions are not listed by server). I'm adding that to the "nice to have" section in the roadmap. Thanks, Willy
