Thank you. That makes perfect sense, though I'd really like to be able to tune the DTU side. Many of our DTU's have no human attached, and are running custom kiosk sessions. At the moment of the disconnection, I'd love for them to dynamically rebind to an available server and restart their display. Waiting 20 seconds in this environment is an eternity.
What can we pay you to make this happen? ;-) -Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Joerg Barfurth Sent: Tuesday, September 08, 2009 11:39 AM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] auth.props timeout tuning (was RE: Detect Disconnected DTUs) Quayle, Bill schrieb: > This brings up a good point. > > In my installation, our production FOG is split across two > datacenters. If I "lose" one datacenter, I want the clients to fall > over to the servers at the other datacenter as quickly as possible - > in seconds would be ideal. > That is the other side of the connection. Here the DTUs need to notice that the server is non-responsive. They react much quicker than the server does. IIRC the timeout 60 is sec (+/- 20 sec), but not configurable. An interactive user may expedite this by rebooting the DTU when the server seems to be gone. > As a matter of fact, if I have *any* problems with a server, I want > the DTU to re-bind to another server quickly so I can get my displays > back online. > > Can I tune this using the timeout value in auth.props, and what is > the downside to this? > The auth.props timeout won't help you, as it only affects the server timing out lost DTUs connections. If you have lost a data center, you are not really worried about what the lost server does in its disconnected closet. Instead you care about the DTU side (which is not configurable). If you want the server to detect lost DTUs more quickly, so that it generates disconnect events and frees resources, then you may reduce the timeout value in auth.props. According to the man page such modifications are not supported, but I would not expect problems unless you reduce it below ~25 sec: Normally the DTUs send a heartbeat message every 20 sec. If the server regularly times out before that interval, the dynamics of the server-DTU heartbeat interaction will be changed significantly. - Jörg -- Joerg Barfurth phone: +49 40 23646662 / x66662 Software Engineer mailto:[email protected] Desktop Technology http://reserv.ireland/twiki/bin/view/Argus/ Thin Client Software http://www.sun.com/software/sunray/ Sun Microsystems GmbH http://www.sun.com/software/javadesktopsystem/ _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
