Willy et al, RDP persistence, wow that is good news...
2009/7/23 Willy Tarreau <[email protected]> > > Hi guys, > > I definitely see a problem. Timeouts are too short for RDP (50 seconds). So > after that time, if the client does nothing (eg: talk on the phone), his > session expires. From what I've heard, people tend to set session timeouts > between 8 and 24 hours on RDP. Windows RDP clients send a keepalive every minute and have seemless reconnection's which probably hides the problem a bit (Linux clients crash after 50 seconds) , so yes massive timeout makes a lot of sense. > > > BTW, you might be very interested. Exceliance has developped and contributed > RDP persistence ! This is in the development branch. Check the latest snapshot > here : > > http://haproxy.1wt.eu/git/?p=haproxy.git > > basically, you just have to add the following statement in your backend : > > persist rdp-cookie > Thats fantastic news! Really looking forward to that one.... But has any one looked at doing a SourceIP persistence which is not a hash i.e. a look up table of source IPs? The maintenance of real servers is almost impossible in hash mode...without users on RDP (or other TCP app.) hitting the wrong server. I might play with the aformentioned trick in the meantime though: server TS-1 10.0.0.102 check port 3300 server TS-1 10.0.0.102 check port 3389 backup I guess another option with maintenance is to allow a server weight of 0 (offline for maintenance) and have two options for this: 1) Kill all connections immediately and move to new server. 2) Wait for old connections to timeout, and new connections go to new server. -- Regards, Malcolm Turnbull. Loadbalancer.org Ltd. Phone: +44 (0)870 443 8779 http://www.loadbalancer.org/
